chuckjonas / apex-chainable Goto Github PK

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

Due to the release of theBatchApexErrorEvent, there is a clear advantage in running this process in Batchable instead of Queuable.

The only existing functionality that might be tricky to recreate might be appendLinks(). Still, being able to properly handle limit exceptions is much more important then the abiblity to append actions mid-execution

I think it would be nice to have a way to log arbitrary messages about the execution which might help with debugging but aren't wanted in the Action Response.

We could do this by adding a base class method log(String msg) which would just append to a string and then save the result on the Execution Status (see issue #1).