Is it possible to edit (read only) content models and batch processes?

Jeff

I have published a few content models and batch processes from the Demo database to my own database. Once I get them to my database I can't make any changes because they are read only. I also have a working batch process but can't publish it to run a batch because it is read only. Any ideas on this?

jongoesboom

If you are wanting to edit something that has already been designated as Read Only you will need to take the following steps.

1. Select the object that you want to edit. In you case @Jeff it looks like you want the FileShareImport batch process.

2. Go to the Advanced tab and click on Lock Node.

3. Your General Info tab should look similar to the one below with any combination of ReadOnly or ContentsReadOnly checked.



4. Make sure that ReadOnly and ContentsReadOnly are unchecked and click on Unlock Node.

You should now be able to edit the contents of that object.

There is another way to do this that is more effective if you have published over something like a Content Model that has lots of child objects that are also ReadOnly.

1. Again make sure that you have the object selected and click on Edit > Clear Branch Attributes

2. The Clear Branch Attributes message box should pop up and look something like the below picture.



3. Uncheck ReadOnly and ContentsReadOnly and click on OK

This should clear read only out of all of the current object and any child object's properties and you should be able to edit or delete from there.

[Deleted User]

When publishing from one Grooper repository to another, the "Publish To" window has a property for Publish as Read Only.  Setting this to False will allow the published objects to be edited in the destination Grooper repository.

For Batch Processes, best practice is to first Unpublish the process (if it has been "Published" to be used as a production process) using the Unpublish button on the process itself.

Then you can use the Publish To option to publish the process from one repository to another.

Jeff

What about deleting? Everything is grayed out. Can't delete or edit

Jeff

That did it. Thanks!

[Deleted User]

Alternatively (to what @jongoesboom said), you can use the Publish To command again to publish the same nodes that you did previously, only this time set Publish as Read Only as False and change the Publish Mode in the upper right to Update.

Update means that the objects you have selected to publish already exist in the destination (identified by its GUID), so this feature becomes useful when using multiple instances of Grooper in a Test/Production scenario.  In your case, you're updating whether or not the objects are read-only.