Add your voice to the dialogue; share your best ideas!Vote for the ideas you like; it helps to set priorities.
Legacy ID: MER-I-185
Idea created at: 2018-Nov-06
Rudi Pieters Nov 22, 2018 Is this to differentiate between a master and a revision under change, or is this also relevant within a project? email@example.com Feb 7, 2019 This is so that the users of our documents (Sales, Service, Support) can access the latest released document.
firstname.lastname@example.org Feb 7, 2019 (we currently do not use master document functionality)
Rudi Pieters Feb 11, 2019 I can see 2 ways to achieve this with current functionality: 1. Use Projects (or Managed Change folders, which do not require an additional license), this separes published documents from documents under change. In this way, consumers can access the documents in PowerUser/PowerWeb, but it would probably require significant changes to the configuration. 2. On release, publish documents to an Explorer repository where consumers will access them. In this case configuration changes would be small but the consumers would need to switch to another client.
You won't be notified about changes to this idea.