Changes between Version 1 and Version 2 of S3/S3AAA/RecordApproval


Ignore:
Timestamp:
09/14/12 11:57:52 (9 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • S3/S3AAA/RecordApproval

    v1 v2  
    9696...reject it.
    9797
    98   '''NOTE:''' resource.reject() is much more rigorous about record deletion than delete() - it will try to ignore any RESTRICTs and rigirously delete any dependency, because otherwise unapproved records could still leave a legacy behind which is not desirable. However, that means that reject() must always be properly authorized and strictly limited to unapproved records in tables which require approval.
     98  '''NOTE:''' resource.reject() is much more radical about record deletion than delete() - it will try to bypass any RESTRICTs and rigirously delete any dependency of the rejected records so they can not leave any undesired legacy behind. However, that means that reject() must always be properly authorized and strictly limited to unapproved records in tables which require approval.
    9999
    100100  '''Developer note:''' ''GET to {{{approve}}} or {{{reject}}} shall forward to {{{review}}} (for REST compliance)''
     101
    101102  '''Developer note:''' ''If {{{approve}}} or {{{reject}}} are called without record ID, they shall raise a "Record Not Found" error rather than to approve/reject all unapproved records as per the requirement that a record can only be approved/rejects after it has been reviewed (=no bulk approval/reject).''
    102103