Uploaded image for project: 'PrintTalk'
  1. PrintTalk
  2. PTK-138

add discussion of business object life time to Building a system

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Implemented (View Workflow)
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0-IP-3
    • Component/s: Workflow
    • Labels:
      None

      Description

      see title

        Draft

        Table 3.5: Invoice Element

        Expires DueDate ... Date/time when this Invoice becomes Invalid. This date is @DueDate SHALL specify the due date when the payment for this Invoice is due and after
        which a subsequent Invoice MAY be sent and MAY contain late payment fees.

        5.X Life Time of Business Objects <After Life cycle of business objects see PTK-194>

        Some Business Objects such as Quotation or PurchaseOrder may only be valid for a given period of time. These Business Objects have an @Expires attribute, that defines the date and time when a proposed contract is no longer binding for the sending party unless it is either confirmed or refused. A Business Object that has neither expired nor been confirmed is a "Pending Business Object". A Pending business object can be confirmed by sending the appropriate Business Object as defined in table <##ref business object interactions> that references the pending Business Object. A Pending business object can be explicitly refused by sending a Refusal that references the pending Business Object.

         

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  prosi Rainer Prosi
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: