ExecuteCurrentActionAgainOnce
Hans Karlsen (talk | contribs) (Created page with "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 a 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") |
(Replacing message template with parser tag) |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
<message>Write the content here to display this box</message> | |||
ExecuteCurrentActionAgainOnce is tightly coupled to rest calls to external services. | 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 | 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 07:35, 17 June 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 95 days ago on 06/17/2024. What links here