@Miyurumala is there a support for this request from customer order side? If there is a projection that can be used in a Workflow to achieve this.
Note that ifsBpaExecutionUserId internal input variable is deprecated in 24R1 and will be obsoleted in 24R2. From 24R1 it is recommended to use following 2 new internal input variables. ifsBpaCurrentUserDirectoryId - Holds the current directory ID. In some cases like SSO, the ifsBpaCurrentUserDirectoryId and the ifsBpaCurrentUserId are non-identical. ifsBpaCurrentUserId - Holds the current user ID.
This capability is still not there. Not until 24R1.
I meant that this capability won’t be available in 24R1 as well. Not sure if this will be planned for any release beyond 24R1.
You can use a user interaction Workflow for this as suggested in the link given in the previous comment. Here are the documentation that would be useful.User interaction Workflows - https://docs.ifs.com/techdocs/23r1/040_tailoring/500_business_process_automation/020_what_are_workflows/#user_interaction Example of ‘Building a User Interaction Workflow’ - https://docs.ifs.com/techdocs/23r1/040_tailoring/500_business_process_automation/030_getting_started_with_workflows/#building_a_user_interaction_workflow
If I were to troubleshoot this error I will start with enabling observations. Then troubleshoot from the inputs received in observation(https://docs.ifs.com/techdocs/23r2/040_tailoring/500_business_process_automation/040_workflow_tooling/?#troubleshoot_an_execution) Why I do this is that sometimes the inputs that are received to the Workflow may not be the ones that are actually expected and using observations I make sure that I’m not using different inputs for debugging. Then in designer I might be able to observe where the red eye icon is seen. Then I will know which task the error is generated. Next if it is a projection task I will make sure the parameters sent to the projection is correct and the data types are correct. I will most probably compare it with the same projection called from web client, probably using chrome dev tools to see how and what is sent as the payload. Another way is to issue the same call from postman and compare. Parameter names, values, data types, case of
Hi Bryan,What did you mean by ‘check currently running Workflows’? How did you do that?/Lahirumala
If a field is not editable at database entity level I don’t think there is a way you can edit it from a Workflow. Not even by Entity Service APIs.
Did you check any other event action type other than Workflows? If no other type of event action works as well, we can narrow down to the issue being in the custom event.
Yes. Workflow observations is there from 23R2. But even so, still you can use the contents of the attr column in BPA_ASYNC_SYS_TAB as inputs and try to debug the Workflow in inspect mode and check the expected behaviour is there. Sometimes troubleshooting like this helps to isolate the error since we are using the actual inputs.
Hi @bdoucette , If there’s only the event action in attr column that means no data has passed from the custom event to the workflow. Is that intended? If data are passed to the Workflow from the event they should be seen in attr column. If data are supposed to come into the Workflow please check if correct columns are added in the custom event./Lahirumala
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
