You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the status is just tracked directly on the Chainable_Link__c object. This makes it easy to access the result, but unfortunately complicates scenario's where a link gets run multiple times.
I think it would make more sense to track the status as a separate child object:
Chainable_Link_Execution__c
Chainable_Link: Master-Detail
Execution_Date
Status: Picklist
Error_Details:
Response: LONG Text String (or maybe even attachment?)
Response_Type*: ONLY if we decide that the response could be set dynamically at runtime. Otherwise the Chainable_Link__c would track the response type
The text was updated successfully, but these errors were encountered:
Currently the status is just tracked directly on the
Chainable_Link__c
object. This makes it easy to access the result, but unfortunately complicates scenario's where a link gets run multiple times.I think it would make more sense to track the status as a separate child object:
Chainable_Link_Execution__c
Chainable_Link
: Master-DetailExecution_Date
Status
: PicklistError_Details
:Response
: LONG Text String (or maybe even attachment?)Response_Type*
: ONLY if we decide that the response could be set dynamically at runtime. Otherwise theChainable_Link__c
would track the response typeThe text was updated successfully, but these errors were encountered: