C4C has an interesting quirk (I wouldn't go so far and classify it as a bug):
Assume you have a reuse function that returns a value.
In this case, you need to make sure that your script always (i.e. in all scenarios) explicitly (i.e. using the return statement) returns a value.
If you don't, it will return the same value it returned when it was previously called.
When you maintain a communication system in SAP C4C for integration with an SAP backend system (ERP, S/4), you flag the "SAP Business Suite" field and then maintain the "Business Instances".
The terminology has always confused me, but I just came across a pretty old blog by SAP that explains these fields under a somewhat unintuitive title: Communication System Setup and Message Header Hand... - SAP Community.
For a few months now, whenever I've opened a solution in the new Visual Studio 2022 SDK plugin, I've been receiving the annoying warning that my project targets an unsupported version of .NET, asking me whether I want to upgrade the target to .NET 4.8.
It was a mere nuisance, usually clicked okay and could continue to work.
In the new Visual Studio 2022 plugin, it is not possible to create script files (or perform other BO operations) without first checking out and making a dummy edit to any custom BO.
I had created a custom BO yesterday and wanted to proceed with the script files today, when I noticed that I couldn't create them:
The following is the process for installing SAP Cloud Application Studio via the "Visual Studio 2022 plugin" avenue:
According to SAP note 3053335, workflow rule actions that are scheduled “OnSave” are executed BEFORE the BeforeSave. Accordingly, the BeforeSave cannot influence the OnSave action.
However, SAP can enable a backend flag, called “Late Condition Evaluation”.
With that enabled, OnSave actions are executed AFTER the BeforeSave and therefore the BeforeSave suddenly has an influence on the OnSave action.
Some background information recently obtained via an SAP incident regarding the finalize logic (finalize means that BeforeSave is triggered):
In case you're facing a C4C dump (500 Internal Server Error), create an incident from it and find that the the Incident Context => /SAP/ABAP/RuntimeError file shows the error "Object instance creation of action rejection implementation class "<PDI solution namespace>_CL_ACTION_VALIDATION" of action "<PDI solution namespace>_<ID>" on node "ROOT" in BO "<BO>" failed" - you have to do a full solution activation to resolve the issue.
If you want to add an extension field to the standard c4codatapi service via Cloud Application Studio, you will find that "c4codataapi" is not listed in the ODATA dropdown when you create the ODATA Extension (.xodata) object.
Quick note to self: The SAP blog that mentioned that an exported solution is deployable in up to 2 future releases is here.