Ignore:
Timestamp:
10 Jun 2011, 15:41:32 (13 years ago)
Author:
uli
Message:

Maintain history of objects in a separate component, similar to workflows, instead of storing everything with the object core object.

File:
1 edited

Legend:

Unmodified
Added
Removed

  • main/waeup.sirp/trunk/src/waeup/sirp/applicants/interfaces.py

    r6337 r6339  
    283283    state, depending on use-case.
    284284    """
    285     msgs = Attribute('Workflow transitions with date of transition.')
     285    history = Attribute('Object history, a list of messages.')
    286286    state = Attribute('Returns the application state of an applicant')
    287287
    … …  
    402402    """An applicant.
    403403
    404     Here we can repeat the fields from base data and set the `required` and
    405     `readonly` attributes to True to further restrict the data access. We cannot
    406     omit fields. This has to be done in the respective form page.
     404    Here we can repeat the fields from base data and set the
     405    `required` and `readonly` attributes to True to further restrict
     406    the data access. We cannot omit fields. This has to be done in the
     407    respective form page.
    407408    """
    408409    screening_score = schema.Int(
Note: See TracChangeset for help on using the changeset viewer.