Natalia Parra (NataliaP)

NataliaP Member since 2019 2 posts
Posted: June 12, 2019
Last activity: August 22, 2019
Posted: 12 Jun 2019 18:42 EDT
Last activity: 22 Aug 2019 7:20 EDT

Moderate Guardrails - Utility type instead of Activity type

The situation that we´re having is that we know that we can use “Utility” if the activity is called from a “Flow”.

But we have the below scenario:

The task of this activity (Image attached) is to set the error messages, This acction cannot be done using a Data Transforme, for this reason we need to use the activity type in this case. (Obligatory).

We want that the system be able to trigger the validation when the user input the values with out clicking the “Submit Button”, so the solution that we implemented is creating an activity and invoke it from a section.

We can use “Utility” instead of “Activity” so we can avoid the warning message.

The question is, what is the best practice that we can follow ?

***Edited by Moderator Marissa to update platform capability tags****

Low-Code App Development Data Integration Java and Activities Case Management
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.