Add String Data to Input Mapping fields on an API Action Call

[MartyMcCormick]

Hello

I have a simple approval workflow that results in an API call to create a project in S/4HANA Cloud. When you map the Inputs from the data type to the API fields in the Action mapping, you can only select fields.

1. How can I append string values to the fields submitted? For example, if I wanted OrgID to have another 3 character reference after it? Unlike some other areas like email address I cannot type in these input boxes.

2. How can I create static string data in these fields? For example, if I wanted to populate the OrgID in the automation versus have the Build App submit it, what is the best approach?

Thanks,
Marty

[Dan_Wroblewski · Accepted solution]

You could use a decision table to take as input the original string and then output the string with 3 extra characters. Just make a rule where for input you leave it blank (meaning any value) and the output you just make originalString + 'ABC'.

I think this could also work for the static string case.

[MartyMcCormick · Accepted solution]

Thank you very much Daniel, based on some quick testing this will fit the need to update some fields!

[vbalko-claimate · Accepted solution]

It is pitty, that BUILD dont have some kind of expression (if not script, which is more pro code, not citizen developer thing) step for those small modifications and transformations inside project. Of course, you still can use workflow step and make those things in script step inside WFM workflow - but it is quite big caliber for such small thing.

[vbalko-claimate · Accepted solution]

daniel.wroblewski - reading this answer - it came to my mind, that recently we used decision step in customer project (in build proc. aut), but we cant figure out how to update (configure) decision on test/prod environment after promoting (transporting) that process. Only way we were able to make it done was to export on dev and import in test/prod manually and until, the project was not released, we were able to modify decision table. But promoting and importing from CTMS makes that project automatically released (and it is right thing, because dev pipeline), but it prevents also customizing procedures unavailable - and that is strange.

What is right way to do that?

[Dan_Wroblewski · Accepted solution]

Thanks for comments. Are you saying you want a way to update the decision table (or at least some of the values) without having to release and deploy the project again (which is causing you to go through complicated change management)?

[vbalko-claimate · Accepted solution]

daniel.wroblewski ,

In OG times of Workflow management, we created workflows and transported them using CI/CD and CTMS to the test and prod environment. Along with workflows, we created also Business Rules project (using Manage Rule project app), which was used by afforementioned workflow to store data which are dependent on landscape level (dev, test, prod) eg. list of approvers for each approval level, URL for launchpad etc... Those data have to be editable on each level (dev,test, prod), even when the rule itself (meaning structure and implementation of rule) is read only. Usually you have different approvers on prod than on test.

But in BUILD, when I create project which contains DECISION step, and promote (transport) that project to test/prod subaccount, I cannot modify that DECISION. So I cannot set prod approvers, because DECISION table is not editable.

I`m struggling, if it is just some temporary bug, or with introduction of BUILD, the role of Decision step changed and I`m using it in wrong way.

I`m wondering, if this discussion is done on correct place - maybe we should move to mail or some slack channel.

[Archana]

Hello Marty,

Any modifications to the process content is not possible currently. This will be addressed with Expression Editor (in roadmap for Q4) where you can do light weight modifications in the process content with available pre-built functions. In Q2, we are also going to provide the support for SAPUI5 based components as the forms and then you can achieve the needed modifications in the UI5 code itself. For example, you can pass the OrgID as-is and then do the needed splitting or concatenation in UI5 itself.

Value helps are possible only in the Forms and not while mapping the fields. In value help you can choose to have static value or fetch it from backend systems like S/4HANA.

Hope that helps,
Archana