Question
Tata Consultancy Services
GB
Last activity: 20 Jan 2022 13:31 EST
Activity type as Utility
I've seen that when we use the activity type as Utility, I am not getting the usual activity warning. Also, I am able to use that utility type activity in all the places not only in flows as well.
Is that advisable to use the Utility type activities to avoid the activity guard rail warning?
I know that some methods are not supported for Utility type and also won't be able to save the activity if the method is not supporting.
My question here is, can we use utility type activity and use it wherever it required not only in the flows to avoid the guard rail warnings but also wherever the activity is really required?
I've tried the above approach and worked for me.
I just want to know that this a better way of using it.
Thanks
Vaisakh V A
Pegasystems Inc.
FR
I don't think using Utility type on Activities to avoid guard rail warning would be recommended.
I rarely used Utility type unless I need to implement an activity within a flow but that should be quite rare those days.
evoleen.byGecko
FR
@MarcLasserre_GCS I am using an utilty to implement an activity in a flow. it works for the first time, but then it ends the flow. In the second time. in my use case we are able to use the flow multiple times for a claim, is there some restriction for using an utility in a flow or best oractices to implement.
Otherwise i used a background processing and it works but there is the delay of the standard processor so it can create some conflicts, i don t know the solution to that.