ExecuteCurrentActionAgainOnce
No edit summary |
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. | ||
Revision as of 13:53, 28 May 2024
This page was created by Hans.karlsen@mdriven.net on 2024-04-18. Last edited by Stephanie@mdriven.net on 2025-03-13.
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.