Hi Anuj,
Post-Steps are substeps (parts of a custom step type) that execute after a code module executes. There are 4 types of substeps that behave in different ways.
Edit Substeps - Allow the user to configure information at edit time with a step (think of Configuring Limits in a Numeric Limit Test)
Pre-Steps - Execute before your code module. Can be used for configuring a device or some generic setup routine that must be called.
Post-Steps - Execute after your code module. Can be used for error handling or simply carrying out the task of the Step Type.
Custom Substeps - Rarely used. Can be called using the API to perform some special task.
It depends on what you mean by "doing multiple things" with your step types. A large majority of Custom Step Types will have an Edit Substep and Post Substep. Some substeps allow the user to specify the module (Numeric Limit Test, etc...). Some do not (Message Popup, Call Executable, etc...). If you wish to do some common analysis or common actions before or after a user-configured module, it would make sense to allow the user to select a Module. I would almost never use the Default Module (3.5) or Specify Module (3.1 and before) in the Step Type. The reasons for this are discussed in the previous forum post, so I will not repeat them. Since you are doing multiple things, you may want to have several post steps, or one code module that can be used as a post step to do all of these things. If you do not wish the user to specify a module, disable the selection of a module.
Allen P.
NI
