The invoke workflow is one of the oldest and massively used for Robust implementations.
Here is a couple of improvement which would make even better and reduce the number of redundant activities that we include inside the invoked workflow.
Log (incoming and outgoing) arguments
It is very often that we need/want to log arguments values to help us understand the context of our workflow execution and helping troubleshooting a potential issue.
Here is a paint “mock-up” of how this could look like.
This is an idea that we discuss with @Mihai_Dunareanu during the presentation of his Enhanced REFramework quite some time ago which could help to give some data granularity in the reporting without too much effort
The logged value could either create its own log entry or simply added as a log field (of the second activity developed bellow)
This could also be interesting to have this type of feature for some of the core key activities (ex: open browser, giving the option to log the URL variable)
Log Start/End of the workflow
It is also very common to have as a standard to log the beginning and completion of a workflow.
This would then drastically reduce the amount of activity inside what is invoked to have this as an option.
Continue on error
Yes, this can be done in a try catch, but why not give the option to do it in one checkbox and now having to having to click inside the try/catch activity to access the content.
It would also be interesting (as it would be for the current ‘Continue on error’ on activity) to still log the exception occurring.
The current ‘isolated’ option does not seem to cover this scenario either (exception are still throw)
Find all references
Would be nice to be able to right → ‘Find all references/invocations’ on a workflow in the project panel to rapidly find them.
Would also be interesting for the activities.