Open topic with navigation

TIBCO iProcess® Engine 11.9.1

# Export a Procedure Interactively

The interactive method uses the `swutil` menu and displays prompts for each stage of the export. If you want to export a procedure without displaying all of the prompts, use the command line method. See Export Procedures Using Command Line Options.

To export a procedure:

| 1. | Select the following option from the `swutil` menu (see Using swutil):

4 - Export a Procedure

The following prompt is displayed:

    Working, Please Wait .....
    Exporting a Procedure
    Name of Procedure (<CR> to quit?)

| 2. | Enter the name of the procedure that you want to export (as displayed in Procedure Manager).

| 3. | If multiple versions of the procedure exist, you need to specify which version you want to export. You can:

| — | `C`hoose - choose from a list of versions. See step 4.

| — | `A`lways choose - if you are exporting multiple procedures, select this to choose from a list for each procedure without displaying the question.

| — | `S`ame version for all - if you are exporting multiple procedures, you can specify a version number that will be used for all remaining procedures you export.

| — | `D`efault - select this option to use the default version.

| 4. | Choose the version from a list that displays the available versions and their release status. For example,

    There are 5 versions of this procedure:
    0) 1.4 is the default version
    1) 1.1  'm'odel /
    2) 1.2
    3) 1.3  'w'ithdrawn /
    4) 1.4  'r'eleased / 'n'o preference /
    5) 1.5  'u'nreleased /
    Select r,u,m,w,n or index of desired procedure version 0 - 5 :0

Select the version of the procedure to export from the list shown. You can select a version either explicitly, by its version number, or based on its release status:

To select a specific version number, enter the version’s index number - `0`, `1`, `2` or `3` in the example above.

To select a version by release status, enter the appropriate letter. In the example above:

| — | entering `r` selects the current Released version, which is Version 1.4.

| — | entering `u` selects the current Unreleased version, which is Version 1.5.

| — | entering `w` selects the latest Withdrawn version, which is Version 1.3.

The following table shows the full list of release status options that can be shown by the command.

Release Status Options of the Procedure Export Command

Option | Description
`r` | Current Released version
`u` | Current Unreleased version
`m` | Current Model version
`i` | Current Incomplete version
`w` | Latest Withdrawn version. (Earlier Withdrawn versions cannot be selected by status. You must use an explicit version number to select them.)
`x` | Latest Incomplete/Withdrawn version
`n` | No preference

| 5. | If the procedure being exported calls sub-procedures, you must specify the precedence order that will be used to determine the version of each sub-procedure that is exported. This is based on release status, using the same letter codes shown in the table above. For example,

    Change default sub-procedure precedence order (rumiwxn)?
    ‘Y’es change (‘A’lways use new), ‘N’o - default (‘S’kip - always default)

If you choose `Y`, you are prompted to change the precedence order:

    What precedence order should be used for
    exporting any sub-procedures found ?

    'r'eleased|'u'nreleased|'m'odel|
    'i'ncomplete|'w'ithdrawn|'x'|'n'

    Enter order using key above (default is rumiwxn):

Note | If you select an invalid status option, then the sub-procedure will not be exported. To overcome this, it is better to enter a range of status options and include ’`n`’ for no preference. This means that even if the previous status options you have chosen are invalid, the sub-procedure will always be exported. See TIBCO iProcess Modeler Procedure Management for more information about precedence.

| 6. | Choose whether or not to reset the procedure’s extended properties. You can supply new values for each of the following (or leave them unchanged):

| — | `object author` is the name (or other identifier) of the iProcess user who created the object.

| — | `release identification` is free text that you can use to identify the procedure as you want.

| — | `date object created` is the date and time that the procedure was created.

| — | `date object modified` is the date and time that the procedure was last modified.

For each option, you can either respond with `Y`es, `N`o, `A` (Yes and apply to all), `S`kip or `Q`uit

Note | You are not prompted to reset extended properties if the procedure is already OEM locked or is locked by another user.

| 7. | Choose whether to change the procedure’s major and/or minor version number. You can change the major version number, the minor version, or both.

| 8. | Choose whether or not you want to OEM lock this procedure. (An OEM locked procedure cannot be renamed when it is imported.)

Note | If the procedure you are exporting is already OEM locked you do not get this option.

| 9. | If the procedure being exported calls sub-procedures, choose whether you want to export all, some or none of them. For each sub-procedure you export, steps 5 to 7 are repeated.

The procedure and any sub-procedures are exported to the file `SWDIR``\util\``procname``.xfr`. If any `use` files are referenced, a copy of the file (in the iProcess `SWDIR``\``nodename``.n\use` directory) is included in the exported file. Also, any VBA projects used in the procedure are exported.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO iProcess® Engine

Copyright © 1994-2024. Cloud Software Group, Inc. All Rights Reserved.