[jira] [Commented] (OFBIZ-10902) Have a status on agreement records

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OFBIZ-10902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301859#comment-17301859 ] 

ASF subversion and git services commented on OFBIZ-10902:
---------------------------------------------------------

Commit 1b84668aafe2b3ffef40cb3157ec0cda310cc661 in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=1b84668 ]

Improved: Have a status on agreement records (OFBIZ-10902)

Pre-amble

Currently, unlike many other entities, the Agreement entity does not have the
statusId field defined. Agreements, like the other entities, should have a
status (values that help determine the phase of the lifespan beyond
the start- and end date of the agreement), such as:

    Created
    In Progress
    Approved
    etc.

Flows
    Happy flows:
        Happy flow a) created ->b) submitted (for review) -> c) reviewed ->
                   d) approved -> e) in effect -> f) concluded (ended)
        Same, with more flow: a) created ->b) submitted (for review) ->
                   c) reviewed -> d) adjusted -> e) reviewed -> f) approved ->
                   g) in effect -> h) concluded (ended)
    Unhappy flows:
        Unhappy flow: a) created ->b) submitted (for review) -> c) reviewed ->
                      d) cancelled
        Same, with more flow: a) created ->b) submitted (for review) ->
                      c) reviewed -> d) adjusted -> e) reviewed -> f) cancelled
    Prematurely ended flows:
        Nipped in the bud flow a) created  -> b) cancelled
    flows from approval (in effect or in execution) till the end-of-times
        a) approved -> b) in effect -> c) concluded (ended)
        a) approved -> b) in effect -> c) terminated (prematurely ended)

Party Roles

Following Party Roles are involved:

    Agreement Creator - the party (person) that creates, edit, updates and
                        submits the agreement for review
    Agreement Reviewer - the party (person) that reviews the agreement on its
                         merits and impact for the company/organisation
    Agreement Approver - the party (person) that, based on law, regulations
                         and/or business policies approves (or rejects) the
                         agreement
    Agreement Manager - the party (person) that manages the execution of terms
                        of the agreement after the approval till the end-of-times
    Agreement Owner - the Party (party group with roleTypeId INTERNAL_ORGANIZATIO,
                       and  and registered in PartyAcctgPreference) that is
                       legally bound by the agreement

jleroux: this lacks demo data but can still be useful

Thanks: Pierre Smits


> Have a status on agreement records
> ----------------------------------
>
>                 Key: OFBIZ-10902
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-10902
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: accounting
>    Affects Versions: Release Branch 16.11, Trunk
>            Reporter: Pierre Smits
>            Assignee: Pierre Smits
>            Priority: Major
>
> h2. Pre-amble
> Currently, unlike many other entities, the Agreement entity does not have the statusId field defined. Agreements, like the other entities, should have a status (values that help determine the phase of the lifespan beyond the start- and end date of the agreement), such as:
>  * Created
>  * In Progress
>  * Approved
>  * etc.
> h2. Flows
>  # Happy flows:
>  ## Happy flow a) created ->b) submitted (for review) -> c) reviewed -> d) approved -> e) in effect -> f) concluded (ended)
>  ## Same, with more flow: a) created ->b) submitted (for review) -> c) reviewed -> d) adjusted -> e) reviewed -> f) approved -> g) in effect -> h) concluded (ended)
>  # Unhappy flows:
>  ## Unhappy flow: a) created ->b) submitted (for review) -> c) reviewed -> d) cancelled
>  ## Same, whit more flow: a) created ->b) submitted (for review) -> c) reviewed -> d) adjusted -> e) reviewed -> f) cancelled
>  # Prematurely ended flows:
>  ## Nipped in the bud flow a) created  -> b) cancelled
>  # flows from approval (in effect or in execution) till the end-of-times
>  ## a) approved -> b) in effect -> c) concluded (ended)
>  ## a) approved -> b) in effect -> c) terminated (prematurely ended)
> h2. Party Roles
> Following Party Roles are involved:
>  # Agreement Creator - the party (person) that creates, edit, updates and submits the agreement for review
>  # Agreement Reviewer - the party (person) that reviews the agreement on its merits and impact for the company/organisation
>  # Agreement Approver - the party (person) that, based on law, regulations and/or business policies approves (or rejects) the agreement
>  # Agreement Manager - the party (person) that manages the execution of terms of the agreement after the approval till the end-of-times
>  # Agreement Owner - the Party (party group with roleTypeId INTERNAL_ORGANIZATIO, and  and registered in PartyAcctgPreference) that is legally bound by the agreement
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)