ExecuteCurrentActionAgainOnce
No edit summary |
Hans Karlsen (talk | contribs) No edit summary |
||
| Line 3: | Line 3: | ||
See [[Documentation:OCLOperators_RestPost]] | See [[Documentation:OCLOperators_RestPost]] | ||
Its main usage is when a RestPost has failed, and you suspect that the reason for failure is a lapse of an accesstoken valid time. You would then want to silently use the refreshtoken to get a new accesstoken - and once you have the accesstoken you want to ExecuteCurrentActionAgainOnce. | Its main usage is when a RestPost has failed, and you suspect that the reason for failure is a lapse of an accesstoken valid time. You would then want to silently use the refreshtoken to get a new accesstoken - and once you have the accesstoken you want to ExecuteCurrentActionAgainOnce from a special column named onfail in the nesting for the call parameters. | ||
Latest revision as of 13:53, 28 May 2024
ExecuteCurrentActionAgainOnce is tightly coupled to rest calls to external services.
See Documentation:OCLOperators_RestPost
Its main usage is when a RestPost has failed, and you suspect that the reason for failure is a lapse of an accesstoken valid time. You would then want to silently use the refreshtoken to get a new accesstoken - and once you have the accesstoken you want to ExecuteCurrentActionAgainOnce from a special column named onfail in the nesting for the call parameters.
This page was edited more than 7 months ago on 05/28/2024. What links here