Hello Stan, I think the use of sub-processes would support this.
There are 2 options: A *sub process task* is a way of linking in another process. When tasks are created, tasks for the main process are created, along with tasks for the sub process. The linking is done in such a way that the sub process runs all its tasks before passing control back to the main process tasks. I have tested with a 3 level process, which is attached. This is a good way of reusing a set of tasks that are the same in several processes. If using this, the sub process used should not have a starting task set, otherwise it will be assigned before the sub process task has been reached. Note also that you need to be careful when changing the sub process that you also update the version number in the sub process task in the parent process, this is not done automatically. A *start new process action*. When this action is run, additional tasks are generated at run time for the process defined. These additional tasks are run concurrently with the calling process, so slightly different to a *sub process task.* *hope this helps* *Regards/Vaibhav * On Thu, Dec 13, 2012 at 9:43 AM, Stanley Feinstein < st...@projectremedies.com> wrote: > ** > > Hi Tauf.**** > > ** ** > > Thanks for your feedback. The reason you want to have ad hoc tasks is the > always prevalent reality: the 80/20 rule. 80% of the time, the tasks in > the pre-defined process fit the request, but 20% of the time it doesn’t. > **** > > ** ** > > The other purpose is for new processes and enabling your help desk people > to, when they see the need for a new process, use an ad hoc task capability > to create new processes on the fly. The ad hoc task capability should > change any Remedy ticket into a multi-task process on the fly.**** > > ** ** > > You didn’t answer my question: can the process be more than one level > deep. Can it be parent / child / grandchild or more?**** > > ** ** > > Thanks.**** > > ** ** > > Stan Feinstein**** > > w. 310-230-1722.**** > > c. 310-428-5748.**** > > ** ** > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *Tauf Chowdhury > *Sent:* Thursday, December 13, 2012 9:23 AM > > *To:* arslist@ARSLIST.ORG > *Subject:* Re: Any tool similar to Abydos Analyser!!**** > > ** ** > > ** Susan/Stan, > > As a customer, I'll try to answer to the best of my ability. > The reason it doesn't come with ARS is probably because in order to get > your processes that you build to work within Remedy, it needs to leverage > Task Management. That is the underlying engine that your processes use to > actually enforce the flows you build. It's all within TMS. > Because of that, you also cannot insert Ad-Hoc tasks in there as it would > break the pre-built nature of the process flow. The whole idea is to > enforce a standard process. Ad-Hoc would break that in most cases. **** > > ** ** > > On Thu, Dec 13, 2012 at 12:17 PM, Susan Palmer <suzanpal...@gmail.com> > wrote:**** > > ** And what happens if you're not an ITSM user, a custom only shop. Why > doesn't it come with ARS as opposed it ITSM?**** > > ** ** > > On Thu, Dec 13, 2012 at 10:54 AM, vaibhav wadekar < > wadekar.vaib...@gmail.com> wrote:**** > > ** Hello Vikram, > > Abydos analyser is now replaced with Process Designer 8.3.2 and comes with > ITSM 7.6.04 and later. You can download a copy of it from EPD within ITSM > Suite area. > > These are the benefits of process designer > > Process Designer is the quickest and most cost effective way of > implementing new processes such as Change and Service requests. Remedy > customers can quickly and easily implement processes graphically using > Process Designer without resorting to customisation or having to update > multiple complex templates. This means implementing processes takes a > fraction of the time it would without Process Designer. > > Process Designer is a tool for process designers that provides a graphical > interface to build processes that can be executed on Remedy without the > need to develop new applications or customise existing applications or > templates. Process Designer is particularly beneficial for systems that > require multiple different processes and tasks depending on the type of > request such as Change Management, Service Request Management and > Incident/Problem Management. > *The benefits of using Process Designer with Remedy are:* > > 1. Processes that fit the business - Process Designer allows you to > implement processes that fit the business exactly without having to > customise existing bespoke or out of the box applications. > > 2. Business user get what they want - Business users know what they are > getting as they are able to understand and review the process in graphical > form exactly as it is implemented. > > 3. Fast Deployment at lower Cost - Process designers use a simple > graphical interface to implement processes without needing to customise > Remedy. > > 4. Reduced Support and Upgrade Costs - Remedy Administrators have reduced > time and effort in supporting the Remedy applications as there is no > additional development or customisation. Significant effort is also saved > in upgrading as Remedy applications are not customised. > > 5. Streamlined processes – Process Designer allows the automation of > processes through the implementation of automated actions removing the > necessity of manual intervention where possible. > > 6. Adherence to management, compliance and audit requirements – Not only > is the process diagram a self documenting description of the process as > implemented but also the Process Tracker provides a diagrammatic view of > the current status and historical flow of every transaction through the > process. > > 7. Simplified User Interface – Process Designer enables decision trees to > be built quickly to provide a simplified user interface for data required > to support processes. This ensures user productivity and consistent quality > data. > > 8. Automated Version Control – Process Designer includes automated > generation of version-stamped processes so that you can easily roll-back to > or report on usage of previous versions without the need to get into any > workflow development. > > Process Designer provides these benefits through a graphical interface > that allows process designers to build processes that can be executed > within Remedy based on tasks, dependencies, decisions, rules (such as Task > Assignment and SLAs ,actions such as get user data, updates fields and send > emails). > > You can get more info from below link > > https://docs.bmc.com/docs/display/public/itsm80/PDFs > > Hope this helps. > > Regards/Vaibhav **** > > > > > **** > > ** ** > > On Thu, Dec 13, 2012 at 2:20 AM, Vikram <vkulka...@columnit.com> wrote:*** > * > > hi List, > > Can anyone point me to a tool which is similar to Abydos analyser. What we > need is be able to see the system workflow and forms relationship in a > pictorial way instead of doing it ourself via the dev studio and show > relationship feature. > > Is there any such thing avaliable in real which can tell me that this is > my application structure and this is how the forms are related to each > other or I sholud better get going with the manual way of finding it out? > > Thanks, > Vikram > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years"**** > > ** ** > > _ARSlist: "Where the Answers Are" and have been for 20 years_ **** > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ **** > > > > > -- > *Tauf Chowdhury > > ***** > > _ARSlist: "Where the Answers Are" and have been for 20 years_ **** > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <export date="Fri Dec 14 10:44:31 SGT 2012" version="8.3.2"> <process id="000000000000135"> <category>Child Process</category> <status>Live</status> <type>Test</type> <version>6</version> <module/> <sla/> <notes/> <audit>No</audit> <swimlanes>0</swimlanes> <company>Administrator</company> <parent>ABYD:Sample Form</parent> <maintainLayout>0</maintainLayout> <assigneeGroup>1;</assigneeGroup> <task id="000000000000317"> <name>Grandparent process</name> <type>Child Process</type> <pinx>87.0</pinx> <piny>69.0</piny> <order>2</order> <subprocessversion>4</subprocessversion> <category>Test</category> <group>Administrator</group> <retenclosing>No</retenclosing> <tasksla/> <starting>No</starting> <subprocessid>000000000000133</subprocessid> <subprocessname>Grandparent</subprocessname> <description/> <groupsql/> <taskrule/> <audit>No</audit> <width>25.0</width> <height>15.0</height> <outcomefield/> <supportCompany/> <supportOrganisation/> <wizardOutcomeLabel>Please select the outcome</wizardOutcomeLabel> </task> <task id="000000000000316"> <name>Child Task</name> <type>Child Process</type> <pinx>88.0</pinx> <piny>43.0</piny> <order>1</order> <subprocessversion/> <category>Test</category> <group/> <retenclosing>No</retenclosing> <tasksla/> <starting>No</starting> <subprocessid/> <subprocessname/> <description/> <groupsql/> <taskrule/> <audit>No</audit> <width>25.0</width> <height>15.0</height> <outcomefield/> <supportCompany/> <supportOrganisation/> <wizardOutcomeLabel>Please select the outcome</wizardOutcomeLabel> </task> <dependency> <firsttask>Child Task</firsttask> <nexttask>Grandparent process</nexttask> <sharetype>OR</sharetype> <outcome/> <restart>No</restart> <restartsla>No</restartsla> <beginpoint>Bottom</beginpoint> <endpoint>Top</endpoint> <cp1pinx>100.16666412353516</cp1pinx> <cp1piny>61.66666793823242</cp1piny> <cp2pinx>99.83333587646484</cp2pinx> <cp2piny>65.33333587646484</cp2piny> </dependency> </process> <process id="000000000000133"> <category>Grandparent</category> <status>Live</status> <type>Test</type> <version>4</version> <module/> <sla/> <notes/> <audit>No</audit> <swimlanes>0</swimlanes> <company>Administrator</company> <parent>ABYD:Sample Form</parent> <maintainLayout>0</maintainLayout> <assigneeGroup>1;</assigneeGroup> <task id="000000000000313"> <name>GP Task</name> <type>Grandparent</type> <pinx>75.0</pinx> <piny>27.0</piny> <order>1</order> <subprocessversion/> <category>Test</category> <group/> <retenclosing>No</retenclosing> <tasksla/> <starting>No</starting> <subprocessid/> <subprocessname/> <description/> <groupsql/> <taskrule/> <audit>No</audit> <width>25.0</width> <height>15.0</height> <outcomefield/> <supportCompany/> <supportOrganisation/> <wizardOutcomeLabel>Please select the outcome</wizardOutcomeLabel> </task> </process> <process id="000000000000139"> <category>Parent</category> <status>Live</status> <type>Test</type> <version>19</version> <module/> <sla/> <notes/> <audit>No</audit> <swimlanes>0</swimlanes> <company>Administrator</company> <parent>ABYD:Sample Form</parent> <maintainLayout>0</maintainLayout> <assigneeGroup>Administrator</assigneeGroup> <task id="000000000000329"> <name>Child Process</name> <type>Parent</type> <pinx>130.0</pinx> <piny>38.0</piny> <order>2</order> <subprocessversion>6</subprocessversion> <category>Test</category> <group>Administrator</group> <retenclosing>No</retenclosing> <tasksla/> <starting>No</starting> <subprocessid>000000000000135</subprocessid> <subprocessname>Child Process</subprocessname> <description/> <groupsql/> <taskrule/> <audit>No</audit> <width>25.0</width> <height>15.0</height> <outcomefield/> <supportCompany/> <supportOrganisation/> <wizardOutcomeLabel>Please select the outcome</wizardOutcomeLabel> </task> <task id="000000000000328"> <name>Parent Task</name> <type>Parent</type> <pinx>130.0</pinx> <piny>10.0</piny> <order>1</order> <subprocessversion/> <category>Test</category> <group/> <retenclosing>No</retenclosing> <tasksla/> <starting>Yes</starting> <subprocessid/> <subprocessname/> <description/> <groupsql/> <taskrule/> <audit>No</audit> <width>25.0</width> <height>15.0</height> <outcomefield/> <supportCompany/> <supportOrganisation/> <wizardOutcomeLabel>Please select the outcome</wizardOutcomeLabel> </task> <dependency> <firsttask>Parent Task</firsttask> <nexttask>Child Process</nexttask> <sharetype>OR</sharetype> <outcome/> <restart>No</restart> <restartsla>No</restartsla> <beginpoint>Bottom</beginpoint> <endpoint>Top</endpoint> <cp1pinx>105.83333587646484</cp1pinx> <cp1piny>29.33333396911621</cp1piny> <cp2pinx>106.16666412353516</cp2pinx> <cp2piny>32.66666793823242</cp2piny> </dependency> </process> </export>
