Convey to the JDBC connector default status of assets"
Hello all,
Is there a way to tell the JDBC connector used by Jobserver for metadata ingestion to create assets with some default status like “Implemented”.
Currently, I think it picks the “Candidate” status from “Global Assignment”. I can move the “Implemented” status up there so that it comes the first status. But, other projects in the environment do not agree to do that. I can create a workflow to update the status but wanted to check if I can populate the default status at the JDBC connection level (as this would be the easiest & simplest option)
noor
Posted 4 years ago · Edited 1 year ago·Last reply 4 years ago
1 comment
alvinuseree
·4 years ago · EditedThe trick here is where the Catalog metadata lands when ingested for the first time.
It lands in the Schemas Community. You could add another scope there that has the Status “Implemented” at the top of the list.
Now, this only covers newly ingested metadata and not metadata created as a result of a refresh.
I know a fair few clients ingest into the Schemas Community then move the metadata to the respective Business Communities afterwards - which can be a bit problematic here.
I’d say under those circumstances, you could have a workflow to either change the status automatically or another workflow that flags to the Owner that a newly created asset has come about as a result of a refresh and to Approve of it (in turn, changing the Status to Implemented).
In my head, this solution works quite well as you don’t have a workflow that covers the initial ingestion and instead one that covers changes only - which I imagine should reduce the scope of the workflow and make for a bit more of a robust solution.