Prevent Users From Accepting Or Rejecting Changes But Still Able to Disable Change Tracking

[dreifsnider]

Hi,

I know we can set ChangeTrackingInitialState='FORCED' to prevent Web Author users from accepting/rejecting other's changes, but it also prevents users from disabling change tracking.

We have a use case where a user would need to disable change tracking (deleting a table column), so we're hesitant to set ChangeTrackingInitialState=FORCED. But we still want to prevent users from accepting/rejecting other's changes.

Is it possible to do this without setting ChangeTrackingInitialState=FORCED?

Thanks!
Daniel

[mihaela]

Hello,

For delete table row we already added a "changeTrackingBehavior" parameter that can be set to allow the operation to be executed when change tracking is activated:
https://www.oxygenxml.com/doc/versions/ ... oblem.html

I think a similar approach can be applied on delete column operation, if necessary.
If you use a custom framework you could extend the default delete column operation and implement getArguments() method to return the ro.sync.ecss.extensions.commons.table.operations.AbstractTableOperation.CHANGE_TRACKING_BEHAVIOR_ARGUMENT. Then, in your framework you could use this operation and set the changeTrackingBehavior to "Allow with change tracking disabled".
We will add an issue to add this parameter in the built-in operation.

Best Regards,
Mihaela

[dreifsnider]

Hi Mihaela,

Thank you for your reply! I remember this coming up previously and we were investigating extending the delete table column operation.

I was more hopeful that there would be a way to still show the track changes button when ChangeTrackingInitialState='FORCED' is set, and leave all the other existing functionality of ChangeTrackingInitialState='FORCED' (users can't delete another's changes).

Our primary use case for ChangeTrackingInitialState='FORCED' is to prevent Web Author users from accepting/reject changes within Web Author as we want our technical writing team who use Oxygen Desktop to be the ones who accept/reject changes.

If this isn't possible then we will implement extending the delete table column operation to set the changeTrackingBehavior to "Allow with change tracking disabled" as you mention, but this is possibly a greater undertaking for us.

Thanks!
Daniel