Suggestion: I'd like to suggest you update this tab values to an expression, so we can set constant values instead of literal values
All of the other tabs already have their values as expressions.
Reason: I'm having a 'corno job' changing more than 300 processes by hand. If I could change this to a constant, it would be easily changed by the next unfortunate one that needs to update this by just changing one constant.
Discussion posts and replies are publicly visible
I've always been thinking this is more of a safeguard, since changing the process model archive settings will take immediate effect on all process instances in the system for that process model, also preventing us from setting these values dynamically for different instances, with the current platform. I learned this early on in the Portal days, where process instances in-memory were necessary for reporting. Lowering the process model archive settings immediately archived completed process instances, removing them from those portal reports.
For "updating process variables", are you attempting to add/remove PVs in running instances or just update theri values? For bulk updates to pv values, I've always scripted that through 1 process which loops the Set External PVs service of the Get and Set External Process Variables plugin, based on process instance IDs retrieved from queryProcessAnalytics.
Chris said:For "updating process variables", are you attempting to add/remove PVs in running instances or just update theri values?
I assumed Arthur wasn't referring to "PV" process variables but rather the archival days values, i.e. where there are several hundred process models all hardcoded to 7 days and the customer decides that value should be updated to 10 days etc... though I guess I could be reading it wrong(?)
I wasn't sure on that either..
Additionally this may be a time for consideration of changing these processes to use the System Default, then update that default as necessary, depending if this is the majority or minority of process models.
Yeah. I actually didn't know the trick about the archival setting immediately changing the same for all current instances. I might be able to use that in the future and *also* it's probably the reason my original answer isn't feasible, lol.
Alternatively I think maybe there shouldn't be just 1 "system default". Maybe "high/medium/low" settings? You could set one to 0 - 2 days, one to 5 - 7, and one to 10 - 20, for example.