Open topic with navigation

TIBCO iProcess® Engine 11.9.1

# Import a Procedure Interactively

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

To import a procedure (the following example uses a procedure called `APPLY1`) using the `swutil` menu:

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

7 - Import an ‘`xfr`’ file

The following prompt is displayed:

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

| 2. | Enter the name of the `.xfr` file that contains the procedure you want to import.

For example, if the procedure definition file is called `apply1.xfr`, enter `apply`.

| 3. | If the procedure already exists on the target system, you cannot overwrite it. The following prompt is displayed:

    Checking Procedure ‘APPLY1’:
    Procedure name APPLY1 already exists
    ‘R’ename, ‘N’ew version or ‘A’lways new version?

Instead, you must choose one of the following options:

| — | R Rename the procedure.

(You cannot rename an OEM locked procedure. If you do, the import attempt will fail.)

Name of procedure (`<CR>` to quit).

| — | N Create a new version of the procedure, in which case the minor version number is automatically incremented.

| — | A Always create a new version. Select this option, if you are importing more than one procedure and want to create a new version for each one. This prompt is then suppressed for any remaining procedures during this command session.

| 4. | If you chose to rename the procedure, you are prompted to enter a new username for the owner of the procedure. If you chose to create a new version, go to step 5.

    Do you want to change the default owner - owner?
    Yes, No, A yes and apply to all, Skip all

You can choose one of the following:

| — | `Y`es - and then enter a new username.

iProcess checks that this username is a valid iProcess user, but does not verify that the user has the appropriate permissions on the procedure. You must ensure that the specified username has appropriate access to the procedure.

| — | `N`o - and use the existing username.

| — | `A` - and then enter a new username and this will apply to all remaining procedures being imported.

| — | `S` - responds No to all and sets the owner to the user performing the import.

| 5. | If you are importing a procedure to an iProcess Engine that has case data normalization enabled and the procedure you are importing does not (for example, it may have come from an earlier iProcess Engine version that does not support case data normalization), then you are prompted to import the procedure with case data normalisation enabled.

    Enable Case Data Normalization for the current procedure?
    ’Y’es, ’N’o, ’A’(Yes and apply to all), ’S’kip (No to all ):

You can choose one of the following:

| — | `Y`es - to enable case data normalization.

| — | `N`o - to import the procedure without case data normalization enabled.

| — | `A` - yes to enable case data normalization and apply this to all remaining procedures being imported.

| — | `S` - no to enabling case data normalization and apply this to all remaining procedures being imported.

| 6. | You are prompted to overwrite the procedure description. Select `Y` to overwrite the procedure description, or `N` to use the existing procedure description.

| 7. | Enter the new release status for the procedure. The available options are determined by the following factors:

The release status of the procedure in the `.xfr` file, as shown in the following table:

Procedure Release Status in .xfr and Available Import Options

Status in .xfr file | Available import options
Incomplete | Incomplete, Withdrawn
Unreleased | Unreleased, Withdrawn
Released | Model, Released, Withdrawn
Model | Model, Released, Withdrawn
Withdrawn | Withdrawn

The current release status of the procedure versions on the target system (if you have chosen to create a new version of a procedure that already exists).

The status that a procedure can be imported as depends on the status of any existing versions of the procedure on the system, as shown in the following table.

Procedure Release Status on Target System and Required Conditions for Import

Status to be imported | Required conditions for import
Unreleased or Incomplete | If there is not already an Unreleased or Incomplete version of the procedure on the system.
Model | If there is not already a Model version of the procedure on the system.
Released | If there is not already a Released version of the procedure on the system. If there is, then you will only be able to import the procedure as Withdrawn.

| 8. | (Optional) Specify whether or not you want to import the table data for any tables used by the procedure. This only appears if the procedure contains any tables.

Note | TIBCO recommend that you import table data, otherwise you may experience problems when you edit the procedure definition or try to start cases of the procedure.

| 9. | (Optional) If the procedure uses sub-procedures, steps 3 to 5 are repeated for each sub-procedure.

| 10. | You are prompted if you want to import another procedure. Enter `Y` or `N`. If you enter `Y`, continue from step 1.

The procedure is imported to the root Procedure Management library. If you want to move the procedure to another library, use Procedure Manager to do so. See "Moving and Copying Procedures, Libraries and Shortcuts" in TIBCO iProcess Modeler Procedure Management.

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.