Details
-
New Feature
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
None
-
None
-
None
-
Pulsar
-
Pulsar 252 -DocTypes & Gateway, Pulsar 253 -DocTypes & Gateway
Description
An approval flow is needed to move the changes in the developer branch to the core(master) branch to make them available in production. Projects GUI would be the right place for the overall flow, including for document types. We would just need to show that document types are associated with the project in the projects GUI somewhere. The changed document types can be listed in a separate tab next to the lists of channels and documents. Beside these, there are some more discussions on this in the technical design document which may/should also be taken into account.
In addition to that, if the document type is newly created both core and developer branches of the document type should be published together in developer project.
Attachments
Issue Links
- relates to
-
CMS-14125 Integrate projects feature workflows with document type editor in brX SaaS
- Closed
-
CMS-14265 Support single developer project for doc types on projects
- Closed
-
CMS-14128 Support single development project on document type editor
- Closed
-
CMS-14127 Remove commit menu on document type editor in brX SaaS
- Closed