This component executes an executable file (such as an MSI) and waits for the application to finish running.
[Insert component icon image file here.]
Property
Description
Done
When the application has finished running, this path is followed.
Error
This path is followed if the component encounters an error while it executes the process.
The properties on the Process tab in the Execute Process and Wait (Run) component are listed and described in the following table:
Section
Process
File Name
Lets you enter the value for the name of the file to be executed, as it appears in the directory.
If you do not use a Working Directory, supply the full file path to the executable file.
Arguments
Lets you enter the input values necessary to run the executable file
Outputs
Standard Output
Unknown
Output
Standard Error
Output Error
Advanced
Verb
Lets you select a value for the command-line verb (such as open or print).
Working Directory
Lets you enter the value for the directory where the file to be executed is found.
If you use a working directory, use the Use Shell Execute property.
Window Style
Lets you select the style of the command-line window that opens.
Normal
Hidden
Minimized
Maximized
Create No Window
Lets you select whether to display the command-line window.
Use Shell Execute
Lets you select whether to use the specified working directory.
The properties on the Settings tab in the Execute Process and Wait (Run) component are listed and described in the following table:
Component Class Name
The class name of this component. This property is not editable, but useful if you call Symantec support.
The description of this component. This property lets you describe how the component is used. You can use it to provide any wanted documentation for this component.
This description is included in the model reports that are created when you click Plugins > Generate Business Model.
Location
The physical location of the top left point of this component on the workflow model.
Name
The name of this component. You can change the name.
If you changed the component name when you double-clicked it on the workflow model, the changed name appears here.
Override Background Color
This property lets you change the background color of this component.
To Do
This property lets you record what you still need to do with the component. Use this property to help you remember the configuration that you want to apply to this component.
The text that you enter for this property appears at the bottom of the component editor. If you enter text for this property, a checklist symbol appears on the component in the workflow model.
Is Enabled
This property lets you enable or disable the component. By default, components are enabled. When a component is disabled, it has no effect on the Project. Uncheck Is Enabled to disable the component.
Execution Outcome
If a component with more than one outcome path is disabled, you must select which outcome path you want the component to take. Click the Execution Outcome drop-down list and select the outcome path for the workflow to follow.
Disabled Mapping
If the component has output parameters, you must configure all output parameters with fixed data to pass on. This configuration can be performed in the Disabled Mapping option.
[If this component connects to a process or product outside Workflow, insert the definition of the connection string and/or authentication requirements to make that connection.]
[Describe any setting options that change the way this component behaves.]
[Name each use case that you include below.]
[Describe the use case. Insert screen shots or package files. Insert a description of how the settings are configured. Insert additional information about the use case.]
120 seconds is the default timeout for IIS. You can adjust that in the IIS manager on the server, but i've never had much luck with it working properly when changed.
Yes, you can execute a .exe program using this component; but I've had a problem ( exception occurrs ) when run a console program process that uses more than 2 minutes of execution time. :-(
Can I use this to exicute a program on the workflow server?
You could try running "msiexec /i <path to msi>".
Also, this message should probably be moved to the Workflow forums.
Hello, one question ...
How can I do to execute a shell in the local machine? I have seen that the execution is in the host, but i need to execute a MSI (for example) in the client side.
Do you know if is it possible?
Thanks ;-)