1 / 14

ORGWARE

ORGWARE. BAAN IV Enterprise Modeler Editors and Rule Creation. Editors and rules. Business function editors Business process editors Creating rules Working with static conditions. Business function editors . Repository editor New business functions can be added

jaron
Download Presentation

ORGWARE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ORGWARE BAAN IV Enterprise Modeler Editors and Rule Creation

  2. Editors and rules • Business function editors • Business process editors • Creating rules • Working with static conditions

  3. Business function editors • Repository editor • New business functions can be added • Reference and project model editors • Functions can only be copied from repository • Here optimization relationships can and must be added • Project model editor • Phases can be added to business functions

  4. Business process editors • Repository editor • New business processes can be added • Reference and project model editors • Processes can only be copied from repository

  5. Business process repository editor • Automatic relations • Adding components • Modifying lines of control activities • Click line in a state (twice) and drag outside state • Create another junction by clicking the line twice and drag • Change start/end point of arrow on control activity & state • On junction closest to starting point of arrow: • Press the <Ctrl> key and drag junction (steps of 45 degrees) • On junction closest to ending point of arrow: • Press the <Shift> key and drag junction (steps of 45 degrees) • Save (maybe Options, Resource Settings, End, Apply)

  6. Rules • All rule types use the text editor, but .... • Consistency rules => condition and result in editor • Other three rule types => only condition in editor => result in sub session • In the text editor a zoom session can be started from the Options drop down menu

  7. Consistency rules • Syntax:IF <BF, key> AND <BF, key> OR <BF, key>THEN <BF, key> AND <BF, key>

  8. Rules to set parameters • IF <BF, key> AND <BF, key> OR <BF, key>

  9. Rules for transformation • IF <BF, key> AND <BF, key> OR <BF, key>

  10. Rules to set static conditions • IF <BF, key> AND <BF, key> OR <BF, key>

  11. Working with static conditions(What needs to be done) • A control activity does not have a question linked to it So, we must • Define a variable (referred to as static condition) in which to store the answer (Yes or No). The default value of this variable is "No". • Set the value of the variable to "Yes" using a rule • Link (in the editor) the variable to each arrow, includingwhen to follow this arrow (when static condition is yes or when it is no)

  12. Working with static conditions(How is this done - 1) • Double click 1 of the arrows leaving the control activity • Check or uncheck the "Not" check box (Meaning: follow this arrow when condition value is true or false) • Define whether this condition is static or dynamic • Press static condition button to define a static condition • Give the static condition a sequence number and code • Description should not be a question but an answer like: • "Quotation Management" (preferred) • "Use Quotation Management" • "Quotation Management implemented" • Define default value as "No" • Save and exit

  13. Working with static conditions(How is this done - 2) • In the condition field enter the newly defined condition • The description is filled in automatically with: • "Not" (only if the "Not" check box is checked) • The description of the specified condition • Save and exit • Do the same for the other arrow(s) departing from the same control activity, except: • Do not define a new static condition, but use the same one • Modify the "Not" check box (probably) • Note: the description is modified automatically • Create one rule to set the static condition value to "Yes"

  14. Working with static conditions(How is this done - 3) • Checking whether the static condition works: • link the business function, which influences the static condition rule, to two different phases in the project model • In session Maintain Business Processes by Project Model: • Set current phase to phase 1 using the corresponding button • Display process using the corresponding button (not editor) • Check whether the correct part of the process is dimmed • Change the phase to phase two and continue in the same way • Trouble shooting • Is the default value of SC "No" / does the rule set it to "Yes" ? • Is the "Not" check box checked correctly ? • Is phasing correct in BF model / is current phase specified ?

More Related