...
the mediasharing object must exist
the wkfsharing workflow must have been installed
security must allow users to create mediasharing objects to create a proposal (objectdata domain and insert action)
security must allow users to create declined objects to accept a proposal (objectdata domain and insert action) and modify the workflow of a mediasharing object
| Warning |
|---|
CautionThe mediasharing object is also exploited by the synchronization feature. Refer to the documentation of these two features before starting any customization of this object. |
| Warning |
|---|
CautionThe 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. |
...
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 Accept: will accept the proposal and start the declination. Rejecting the proposal will pass into the rejected status and will no longer be accessible. It is not possible to go back! Ignore the statement: applies a mask to the statement, it will no longer appear in home but always in list. An ignored proposal can always be accepted later. Delete: Equivalent to "reject" but the proposal will be physically deleted. Available only if the user has deletion rights on media sharing object instances.
|
|---|
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. |
|---|
...