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
When a plugin runs, or when the workflow runs an item through the back-end, it should store more information about the information it has discerned.
Seeing in the results that a plugin ran, but that a licence couldn't be detected is now meaningless as the oag 0.2 plugin /always/ runs.
It would be useful for us therefore to store the provider record for an identifier, so that we can at least point the user quickly at the resource.
We should also store some information about why the plugin ran, such as url match (and which url it was). This will make it easier to debug and also easier for end-users to provide us with feedback to plugins to work out how to make them work in these cases.
The text was updated successfully, but these errors were encountered:
When a plugin runs, or when the workflow runs an item through the back-end, it should store more information about the information it has discerned.
Seeing in the results that a plugin ran, but that a licence couldn't be detected is now meaningless as the oag 0.2 plugin /always/ runs.
It would be useful for us therefore to store the provider record for an identifier, so that we can at least point the user quickly at the resource.
We should also store some information about why the plugin ran, such as url match (and which url it was). This will make it easier to debug and also easier for end-users to provide us with feedback to plugins to work out how to make them work in these cases.
The text was updated successfully, but these errors were encountered: