Unable to change status type of child assets

(Ryan Archer) #1

I'm having an issue where i can't change the status type to live for the child assets of my custom form. I made the mistake of cascading the status change on the custom form asset which caused a whole list of errors and then left me with just the 'Page Contents', 'Than You' and 'Format Bodycopies' turned Live - and all the other assets are under construction and there is nothing I can currently do to change this.

 

I have tried setting everything back to 'under construction' and starting the process from the beginning. Also a future status change. Removed the workflow and then re applied it. Even tried other status settings.

 

Has anyone experienced this kind of issue before and found a solution for it? I am using latest version of Squiz at the current date (Jan 2016) which is 5.3.1

(Bart Banda) #2

Not really, you shouldn't even need to set it to cascade from the custom form asset as all those children are dependent children. 

 

You could try and run the inconsistent status fix up script: https://manuals.matrix.squizsuite.net/server-administrator/chapters/system-integrity-scripts#system_integrity_inconsistent_workflow_status.php

(Ryan Archer) #3

Yeah, I kinda figured out what has gone on here. In our previous version of Squiz, all we had to have was the parent asset and form contents have the mandatory metadata fields applied according to the schema.

 

But now, all the required metadata values need to be cascaded down on ALL OF THE CHILD ASSETS. This includes the section headers and form elements inside them. Our workflow is setup to prevent assets from going live unless mandatory metadata fields are completed. Never an issue on the child assets until now.

 

We previously were using Squiz Matrix v4.18.4

I can only assume this is now a new standard when using workflows and metadata schemas against custom forms.

(Bart Banda) #4

Do the children have to have the metadata schema applied? They are just form fields and section right? Could you maybe restrict the  sections of the schema to only get applied to specific asset types and not form sections of page contents assets?

(Ryan Archer) #5

Yes Bart, the workflow needs to be revisited - otherwise I can see this tripping up our dev team many times in the future.