...
Technical requirements for the proposal
The content proposal requires the same prerequisites as the content declination plus:
the
mediasharing
object must existthe
wkfsharing
workflow must have been installedsecurity must allow users to create
mediasharing
objects to create a proposal (objectdata
domain andinsert
action)security must allow users to create declined objects to accept a proposal (
objectdata
domain andinsert
action) and modify the workflow of amediasharing
object
Caution | The mediasharing object is also exploited by the synchronization feature. Refer to the documentation of these two features before starting any customization of this object. |
Caution | The wkfsharing workflow is also exploited by the following functionality synchronization. It is not intended to be modifiable within the framework of of a project, please do not modify it or contact product R&D before undertaking any work on the validation of proposals. |
Access declination proposals
All the available proposals are accessible from the standard datalist
: this one will list like any other list the instances available for the current user according to his rights on the projects whatever the status of the proposal.
The latest declination proposals not ignored are also accessible from a back-office home block named content proposals
:
Proposal visualization screen
Proposals are posted in the dataproposedview
action which is similar to a dataview
but streamlined and where the actions are fully owned.
1 | Current status can be "pending", "accepted" and "refused". |
2 | Available actions
|
3 | Detail of the object to accept presents the fields of the object to accept as it exists at this moment. At the moment, the visualization of the proposed object does not take into account the changes made in the configuration screen. |