TIBCO BPM populating option list strategy

[Romeo Casimina 3]

Hi Everyone,

I have a process with a user task and inside it an option list control. However, values of that option list are being retrieved using a service call. This is working fine, but I was thinking if there is a way to do caching on BPM process wherein instead of a service call to retrieve the list to be used on the form, it will retrieve only from the cache. This way we will not always do a service call for every instance of the process as the list rarely changes.I do not want to put an enumerated list on the form / process as potentially the list will change.

Thinking of using BDS as the cache datastore and creating a global data/case class so it is readily available and can easily be retrieved using scripts and create a scheduled job to trigger the service call and update the global data/case class. But this seems like it defeats the purpose of case object and somehow an overkill.

[Adrian Price]

@miotot, placing such information into a global data object would not be a misuse of the global data facility. By definition global data are those whose lifecycle spans multiple cases, and your option list choices do fit the bill.