Uploaded image for project: 'OFBiz'
  1. OFBiz
  2. OFBIZ-5959

Add lifespan fields to PartyRole

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Won't Do
    • Trunk, Upcoming Branch
    • None
    • party
    • Bug Crush Event - 21/2/2015

    Description

      Currently the assignments of roles to parties are boolean (there or not there).

      As stated in a comment below:

      Reopening, as removing a PartyRole from a party can lead to errors.
      ?? Steps to reproduce:??

      See the error shown (attached screenshot).

      Such errors pop up due to referential integrity (used in other entities).

      However, these role assignments also have a lifespan, and PartyRole records are used in specific object role entities (such as: AgreementRole, QuoteRole, RequestRole, etc.)

      This can be achieved by adding fromDate and thruDate fields.

      Attachments

        Issue Links

        1.
        Update SeedData re PartyRole lifespan fields Sub-task Closed Michael Brohl Actions
        2.
        Update DemoData re PartyRole lifespan Sub-task Closed Michael Brohl Actions
        3.
        PartyRole Lifespan fields - Have Resource in ProjectMgr screens/forms work with the change Sub-task Patch Available Unassigned Actions
        4.
        PartyRole Lifespan fields - Have events & services regarding PartyRole work with the change Sub-task Patch Available Unassigned Actions
        5.
        PartyRole Lifespan fields - Have events & services in Scrum work with the change Sub-task Open Unassigned Actions
        6.
        PartyRole Lifespan fields - Have Resource in Scrum screens/forms work with the change Sub-task Open Unassigned Actions
        7.
        PartyRole Lifespan fields - Have events & services in ProjectMgr work with the change Sub-task Open Unassigned Actions
        8.
        Have Agreement screens/forms work with fromDate and truDate Sub-task Closed Michael Brohl Actions
        9.
        Have AgreementRole entity have fromDate & thruDate Sub-task Closed Michael Brohl Actions
        10.
        PartyRole Lifespan fields - Have InvoiceRole entity work with the change Sub-task Patch Available Unassigned Actions
        11.
        PartyRole Lifespan fields - Have Invoice screens/forms work with the change Sub-task Patch Available Unassigned Actions
        12.
        PartyRole Lifespan fields - Have events & services regarding InvoiceRole work with the change Sub-task Open Unassigned Actions
        13.
        PartyRole Lifespan fields - Have BudgetRole entity work with the change Sub-task Open Unassigned Actions
        14.
        PartyRole Lifespan fields - Have BudgetRole screens/forms work with the change Sub-task Open Unassigned Actions
        15.
        PartyRole Lifespan fields - Have MarketingCampaignRole entity work with the change Sub-task Closed Unassigned Actions
        16.
        PartyRole Lifespan fields - Have MarketingCampain screens/forms work with the change Sub-task Open Unassigned Actions
        17.
        PartyRole Lifespan fields - Have QuoteRole entity work with the change Sub-task Closed Pierre Smits Actions

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            mbrohl Michael Brohl
            pierresmits Pierre Smits
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Agile

                Completed Sprint:
                Bug Crush Event - 21/2/2015 ended 26/Feb/15
                View on Board

                Slack

                  Issue deployment