nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

tt_data to instantiate workflows

dhruv_infy

Hi,

I want to instantiate workflow using tt_data. Can anyone please provide me any material to go through as am not able to find anything in formapi and wfdev pdfs. Thanks.

Find more posts tagged with

Comments

Pawan

Hi,

I want to instantiate workflow using tt_data. Can anyone please provide me any material to go through as am not able to find anything in formapi and wfdev pdfs. Thanks.

There is some information given in the wfdev guide regarding tt_data. What version of TS manuals you are looking into?

cute_guy

Hi,

I want to instantiate workflow using tt_data. Can anyone please provide me any material to go through as am not able to find anything in formapi and wfdev pdfs. Thanks.

If you are using workflow modeler to create workflows, try adding these line in manage workflow screen of the admin tab in ccpro ui.

[HTML]

[/HTML]

If you are using workflow builder, check out the available_templates.cfg.example file which has some OOTB configurations.

joindata.rptdesign

Adam Stoller

If you are using workflow modeler to create workflows, try adding these line in manage workflow screen of the admin tab in ccpro ui.

[HTML]

[/HTML] If you are using workflow builder, check out the available_templates.cfg.example file which has some OOTB configurations.

If you/re using "workflow builder" you should have your head examined ;-)

If you're using WFTs the format of the available_templates.cfg entry depends on what version of TS you are using. If you're using 672, I believe the proper format looks very much like the above with the exception of the outer-most element:

<template_file active="true" name="Sample_Workflow" path="some_dir/Sample_Workflow.wft">
  <allowed>
    <and>
      <command name="tt_data"/>
    </and>
  </allowed>
</template_file>

If you're using an older version of TS, it's similar but different, especially if you start adding constraints on branches, roles, and/or users, but using the example above it would be:

<template_file active="true" name="Sample_Workflow" path="some_dir/Sample_Workflow.wft">
  <command_list>
      <command value="tt_data"/>
  </command_list>
</template_file>

Technically, I believe you can use the older format (bottom) even in 672 for WFTs, but it is recommended that you switch to the new DTD semantics.

nipper

Also, one point to note. There is/was a bug where tt_data did not work if it was only used in WFM. You needed an entry in available_templates.cfg as well and then tt_data would kick a WF off.

If you think you have it configured properly and it is still not working, check the forums there have been a few threads about it.

Migrateduser

Also, one point to note. There is/was a bug where tt_data did not work if it was only used in WFM. You needed an entry in available_templates.cfg as well and then tt_data would kick a WF off.

If you think you have it configured properly and it is still not working, check the forums there have been a few threads about it.

Yeah this bug was supposedly fixed in 6.7.1 but it was unfixed in 6.7.2. They claim it's fixed in SP2, but can they be trusted?