Comments (4)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 VivianeBrasil commented Permalink

Very useful this information, and the URL address for the on IBM's Information Center, where is the Workflow Implementation Guide. Thank you!

2 maximo_TND commented Permalink

Hello, May I know what is the Work Flow enhancement in Maximo 7.5 compared to Maximo 6.x?

3 NataliaAraujo commented Permalink

Help information by Test Architect Alex Oliveira Estevam: <br /> Here is the summary of the most impactful changes, such as those listed here: <br /> http://maximotimes.com/maximo/whats-new-in-ibm-maximo-v7-5/ <div>&nbsp;</div> Here is the guide about Work Flow in Maximo 6.x: <br /> http://publib.boulder.ibm.com/tividd/td/ITMax/621_mx_wkfl_imp/en_US/PDF/621_mx_wkfl_imp.pdf <div>&nbsp;</div> --------------------------------------------------------------------------------------------------------------------------------------- <br /> Help information by Maximo Designer and Architect Brian Downey: <br /> This was the only workflow enhancement in 7.5 (fixpack 3). <div>&nbsp;</div> Tpae 7503: Ability to add the last memo from the most recent workflow assignment action into a Communication Template <div>&nbsp;</div> Problem <br /> Currently there is no way to get the very latest memo from the most recent workflow assignment action to display properly in a Communication Template. There have been many PMR's on this topic. <br /> LastMemo is an existing attribute which can be made visible on the start center inbox. A relationship exists out of the box (i.e. :wfassignment.lastmemo) to reference and display it on a Communication Template. However, because the value has not been persisted to the database as the workflow leaves the task node, the value that is put on the Comm Template for that routing line is at best the previous memo. (In fact, by business rule, it is the last non-null memo for the workflow instance). <br /> For support purposes, the common work around for persisting a data value prior to a normal save is to insert an interactive node with nothing but an automatic route action. The workflow process flows through the node silently and because of the database save, makes the now persistent value available to relationships requesting it for such purposes as setvalues or substitutions into comm. templates. Today workflow performs a database save on initiation; on arriving at a task node; on arriving at a wait node; on arriving at an interaction node; and on arriving at a stop node. <div>&nbsp;</div> Design Approach <br /> We will add a new attribute called wfassignment.currentmemo configured like wfassignment.lastmemo i.e. ALN 50, same as wftransaction.memo. We will add a function to capture the memo value written by an interactive workflow user as he or she routes the workflow, and immediately make its value ready to access by currentmemo – for example, on a Communication Template that is referenced on the same action line as the accept or reject that the user selected. <br /> The currentmemo will contain exactly what the user wrote, even if it was nothing. It will never look back for a non-null memo in the memo stack the way lastmemo does. <br /> The new field’s remarks in dbconfig will be (approximate wording) “The most current workflow assignment memo for the workflow instance. Can be used immediately on the workflow routing action, for example as a substitution variable on a communication template.” <br /> Lastmemo functionality is unchanged. Lastmemo’s remarks in dbconfig will be altered to (approximate wording) “The last non-null workflow assignment memo that has been saved to the database for the workflow instance.”

4 Richtan commented Permalink

What does "continuous" means when it was refer to in "Maximo continuous workflow processes"?