We have a list of 100+ enterprise action codes (e.g., CREA for Create, COMP for Complete, etc), which we figure we would map to flow actions. We'd like to record when these actions are taken. It seems like we'd need a table to map rule names to action codes -- and also, try to ensure that the same activity is called each time following flow action processing.
Ideally, we'd simply like to replace the traditional History-Add call (which includes a narrative message), with one that uses our own action code. (Username, action code, timestamp -- from there we could generate the desired narrative message ("Jon completed the case at 4/10 8:46am")
It would be easier for us to manage if we could record this in the FlowAction rule. We could use the custom fields, but I'm not sure if they are stored anywhere on the clipboard through flow processing.
***Updated by moderator: Marissa to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
To borrow a popular phrase, we're looking to "control the narrative." :-)
The string Assignment to ' (complete task) ' completed by performing a ' Step1 ' is not very fungible. We want to store only the short code (along with direct object, such as the filename). It is not for the history audit to format a message at all; the history audit should store the record in as compact a format as possible.
It should be up to our UI rules to format this in our wording.
AddHistory isn't a final rule. If you want to extend that, you should be able to do so. I'd be cautious about leaving an all else fails way to use the OOTB code so messages don't get lost when the unexpected happens. You could also definitely create your own table and map an object to that and then write "Action" reports based off of those objects. Those could say whatever you wanted.
In the FlowAction rule form, there is an option to selectively audit for that Flow Action. If you have your own general parameterised activity or the make use of the OOTB Work-.Audit, you can make sure that only the required readable/sensible auditing is done.
This would ensure that only your SHORTCODE is stored !