Problem in Form step-type

Hi Experts,
I am new to workflow and exploring various step-types of it. I am using FORM step-type in my workflow.
The container element is of the type EKKO and action type is CHANGE.
When i execute the WF by giving a PO number and make any changes in the output and click on save and exit, the changes that are made are not getting reflected in the EKKO table.
Do i need a separate code for updating the table?
Thanks in advance.
Regards
Balu

Thanks for the suggestion Arghadip.
I was going thru a blog on WF step-types, in which it was mentioned that after pressing SAVE AND EXIT button , the data gets saved in the required table from which the container element is created. Hence i thought that additional code is not necessary.
Could u plz tel wher exactly the code needs to be written.
Regards
Balu

Similar Messages

Read Data's from the Form step type at run time

Hi Experts,
I have the 'Form' step type in my workflow and it will displays some values at the Run time. In this form I have one IO field called 'Comments'. So at the runtime manager can Enter the comments on it.
Now my need is I need to get the 'Comments' data from that form. How can I get this value?
Thanks in Advance,
Helps will be Appreciated..

I got the solution.
Thanks All..

Problem in Forms Step in Workflow....

Hi Gurus,,,,,
I have created a simple workflow using a container element a form step and a mail step.
The action for the Form is Approve . I have made 1 field as input and all others as output only and written the code inside the flow logic.
When executing the form I am able to see the initial from screen, but when I click on the APPROVE button, the screen disappers and the details for the selected item are not coming. However, the mail is being sent.
please help....
Thanks in Advance......
Abhi..

When you press the approve button the form will disappear along with the details you have provide. You have to fetch the details from binding from task to Workflow container.
I think you have to use Approve with query.
Thanks
Arghadip

Step Type Problems with TestStand 3.5

I have a TestStand system where I have created some custom step types (Created originally in TestStand 2.0). I've
used these step types successfully in TestStand 3.1 projects with no problems.
With TestStand 3.5 I have a recurring problem that I cannot clear.
Once the custom steps have been added to the system, I re-load my Process model sequence files and resolve type
conflicts by selecting currently loaded types. (Since my process model utilises these steps and was developed under
3.1)
I save the Process Model and then load in my test programs, again resolving type conflicts by selecting currently
loaded types.
So far so good.
However, when I exit the sequence editor I'm ALWAYS being prompted that the NI_FlowControl.ini typepalette file has
been changed.
This happens even when I set the system to have NO Process Model selected and don't load a program! i.e. I open the
sequence editor and shut it down immediately.
1. Why isn't the Sequence editor prompting me that it's about to change the typepalette file?
2. Why is it changing the type? (And at what point is it happening?)
3. I have no indication as to what has changed within the type and where the conflict is coming from.
4. Why is saving the type having no effect whatsoever?
At one point with a configuration it kept telling me that the NI_DatabaseTypes.ini file had changed (and that it was
the only one to change) I experimented by removing that type palette entry (since I didn't use the database steps
with my process model) and it then started complaining about one of the other NI types as being changed! (Is this a
TestStand bug?) or is there a decent explanation?
I've even tried redefining the typepalette files of my step types to create a clean system, but it all falls apart
whenever I try and load an existing test program. No matter how careful I am, TestStand insists on changing loaded
types without telling me or giving me the option to choose what I want to do!! (Note - re-writing the test programs
is NOT an option!)
Any ideas would be welcomed....

Brian,
Have you modified the CommonResults data type? What is the version that you have loaded? I have seen this problem when you have a newer version of a data type than the engine loads on startup. You can fix this problem by either reverting back to an older version of that type (the same as the engine version), or using the following workaround:
In TestStand, open your type palette window. In the Palette pull down ring select "Customize". Create a new type palette and make sure it is the top-most palette in the list. Name it whatever you like. Click "Ok". Now select your NI_DatabaseTypes.ini from the pull down. Go to the "Standard Data Types" tab, select the "CommonResults" type and copy it.
Select your newly created type palette from the pull down, and paste the "CommonResults" type into this palette. Save all of your palettes.
You should no longer be prompted to save your type palettes unless an actual change has been made.

Problems with upgrading interfaces of custom step types

This question is about configuration management of custom step types.
Here at Cummins, we have defined our own custom step types (CSTs) using MyTypes.ini. People all over the company use these CSTs in their seq files.
All these CSTs are calls to individual sequences in a seq file (for simplicity, we'll call this file "Source.seq"). An example CST would be MyStep which calls the sequence MyStep_sequence in the file Source.seq.
What we want to do going forward is: add one more parameter to the interface of this CST. That means, we will add one more parameter to the sequence MyStep_sequence and then upgrade the definition of the step in MyTypes.ini. We don't want to break existing users, and want the future users of this CST to be able to use this new parameter for newer functionality (ofcourse I did think about creating a new CST all together, but that seemed more maintenance in the future).
In order to achieve this, my idea was to check mark the box "Use Default" in MyTypes.ini for the new parameter (I propose this because very few of the new users will want to care about this new parameter). At the same time, increment the version number of the step. So now, when an old file is brought up that was using this step, it should be usable just as is without any modifications (ofcourse it will need to be re-saved). When this step is used now by a new person, he will be able to see the new parameter and either not care about it (leave it checked as "Use Default") or pass a desired input to it.
First question :, does this sound like a good long term approach for maintaining backward compatibility and CM control? Or are there any percieved issues with doing this due to which its recommended to just go ahead and create a new step?
Second question: this seems to work only if the new parameter is added as a the last parameter in the sequence. if I move things around, (for ex: make this new parameter the first parameter of the sequence), it seems to mess things up. I am okay with making the new interface parameter the last one, but just wanted to throw out this observation I made and see if people had any comments..
Third question: to make things a little more complex, some of the other sequences in Source.seq also USE MyStep. But I've realized that the only implication this has is, I'll have to open up Source.seq and re-save it beofore I send it out to the users..?

Hi Anuj,
Answer 1: Yes, this is a good long term approach in regard to compatibility, maintenance, and control.
Answer 2: Yes, as of TestStand 4.0 this is expected behavior, as the programmatic reordering of prototypes is not a supported code generation teqnique.
Answer 3: In short, yes you much open and save every sequence that contains your new CST. Be sure to save your step type first, making sure to increment your version number. This method will ensure that the step type conflict is automatically resolved in files that load this new type. If you forget to increment your version number you will have to manually resolve this conflict.
Thanks
Evan Prothro
RF Systems Engineer | NI

How to create programmatically a new step type in TestStand (to myTypes.ini)

I need to create a new step type to myTypes.ini file programmatically. I have tried to do it with following steps:
- Get reference to engine
- Load type palette files
- creating new step type (engine.NewSteptype() )
- Inserting new type using TypeUsageList.InsertType method. Problem with this is the first parameter. It excpects it to be in a form of PropertyObject, but engine.NewStepType returns it as a StepType object. If I try to use StepType.AsPropertyObject it returns an error.
How to convert StepType object to a PropertyObject?

And here it is in C++:
TS::IEnginePtr mEngine;
SAFEARRAY * typeList;
TS::TypeUsageListPtr typeUseage;
TS:tepTypePtr stepObj;
mEngine = engine;
mEngine->LoadTypePaletteFiles();
typeList=mEngine->GetTypePaletteFileList();
TS:ropertyObjectFilePtr *rgelems;
SafeArrayAccessData(typeList,(void**)&rgelems);
typeUseage = rgelems[0]->TypeUsageList;
stepObj=mEngine->NewStepType();
TS:ropertyObject *property = stepObj->AsPropertyObject();
property->PutName("TestMe");
typeUseage->InsertType(property, 0, TS::TypeCategory_StepTypes);
rgelems[0]->IncChangeCount();
rgelems[0]->SaveFileIfModified(true);
SafeArrayUnaccessData(typeList);

How do I make Step Types in the Type palette be "master" versions which all sequence files on a particular should use? (since this only seems to "half work")

The situation I would like is to have a library of step types which sequence developers can use. Therefore if new step types need to be added, or existing ones modified - all that needs to be done is to roll out a new MyTypes.ini (for example), and the code modules/substeps.
Scenarios:
If I create types in MyTypes.ini (make sure "Attach to this file" is checked, so they get saved here). I can then create a sequence file using these step types. No problem so far.
I can open the type palette, modify the step properties, and save. When I go back to my sequence file an asterisk appears (saying it needs to be saved, even if I have opened it from scratch). The properties have been updated to reflect what is in the Type Palette. Still no problem (Type versions are the same in the sequence file and type palette).
This is where the problem appears:
If I change a step type (in the Type Palette) from using a code module to using a Post-Step substep instead (changing the module adaptor to "None") - any instances do NOT update when you open sequence files. (The same happens vice versa also).
Please note that the "Type version" listed in the sequence file DOES match that listed in the Type Palette - the properties are the same but the manner in which the code modules are called is DIFFERENT! This then can lead to to runtime errors if the old code module has been deleted for example.
The only way around this is to open EVERY sequence file that contains an instance of the step type, and make sure that you have "Apply changes to all loaded instances of this type" checked in the step type properties dialog. This is is not a good solution since files could be missed, and is very time consuming if you have hundreds of sequence files!
What I need is that the Type Palette on any particular station contains the MASTER copies of each type. These are loaded whenever a sequence file is loaded and NOT retreived from the sequence file. As discussed above this seems to work when you modify properties - but doesnt work fine if you change the way in which code modules are called.
Am I doing something wrong or is this a limitation?

I had a system recently containing seven sequence files, approx 20 subsequences in each, and around 10-20 steps in each sub-sequence. Every step (except for the NI non-code module types) was an instance of a step type.
Each one of these steps had an Edit sub-step and a code module called through the code module adapter.
In order to make these into "wrapped up" step types it was decided to move the code module to a Post-Step substep (as also done in the NI-IVI step types) - so that developers cannot fiddle with the code prototype or module.
In order to do this I had to open all 7 of the sequence files, make the changes and then ensure that "Apply changes in this dialog to a loaded instances" was checked. This seems to sort of work, but some steps started causing Error 17502 (System Error) when you configure them (call the Edit substep). Over the course of the past few months I have had to effectively check every instance of a type to see if it works (deleting the step and replacing it when it doesnt). Other strange things happened like some of the step type instances now have the "None" (adapter) icon associated with them - but both still work.
The idea of creating a type-def of a step type is a good one, but frustrating that it doesnt seem to fully work. Why should the sequence file also store a version of the step-type - which is what is effectively causing this problem - why not make it so that if you dont have the step types installed in the type palette - TOUGH! Message Edited by RichM on 03-15-2005 06:55 AM

Cancel button on form of type form on a table or view

I am a newbie for apex. I am using 10g. I have created form on table emp(empno , name , salary ) . Form is of type Form on a Table or View.
Cancel & Save(Apply changes) button are not working at all. so I copied process reset page and execute on condition save button click. But still cancel button is not working. applcation has some other forms of type Form with a Report and are working properly. I have wasted 2 days on this problem.

Hi,
You can do that. If you have the branch to in the same form what you have to do use clear cache for that page. Click on the edit page, click on the cancel button in the left button section. scroll down to bottom and type the page 32 in the Clear cache field. However it is better to have branch to the report page (different page from the form).
Hope this will help.
M Tajuddin
http://tajuddin.whitepagesbd.com

Problem creating job steps variants

Hi Gurus!
I have a problem with job steps creation.
In my program I need to copy the exist job with some condition accords to job steps variants.
But when I create the new job and it steps and variants in SM37, I can not see the variants names, only number.
For example in template that I am copying it looks like that:
No. Program name/command      Prog. type Spool list   Parameters              User Lang.
1              RMCVNEUA                  ABAP                        BW_TEMPLATE       aaa     EN
But in job that I create it is:
Program name/command      Prog. type   Spool list   Parameters               User Lang.
RMCVNEUA                          ABAP                           &0000000000271     ddd     EN
How can I create steps with variant names instead of numbers/indexes?   BW_TEMPLATE instead of &0000000000271.
My code:
CALL FUNCTION 'JOB_OPEN'
    EXPORTING
      jobname          = lv_jobname
      sdlstrtdt        = lv_date
      sdlstrttm        = lv_time
    IMPORTING
      jobcount         = lv_jobcount
    EXCEPTIONS
      cant_create_job = 1
      invalid_job_data = 2
      jobname_missing = 3
      OTHERS           = 4.
SUBMIT (ps_tbtcp-progname) VIA JOB pv_jobname NUMBER pv_jobcount
                                 USING SELECTION-SET ls_cat-variant
                                 AND RETURN.
CALL FUNCTION 'JOB_CLOSE'
    EXPORTING
      jobcount                          = lv_jobcount
      jobname                           = lv_jobname
     direct_start                      = lv_imm_run
   EXCEPTIONS
     cant_start_immediate              = 1
     invalid_startdate                 = 2
     jobname_missing                   = 3
     job_close_failed                  = 4
     job_nosteps                       = 5
     job_notex                         = 6
     lock_failed                       = 7
     invalid_target                    = 8
     OTHERS                            = 9
Edited by: Dani_K on Oct 27, 2010 4:35 PM

No any suggestions?

Problem in creating data type

hi..
i've problem in creating data type in xi after importing idoc from the R/3 sender
plz tell me the basic steps for creating data type in the receiver i.e xi.....
thanks in advance

Hi,
You don't need to create a data type after importing the IDOC.
Idoc itself acts as message type and message interface.
check this for creating a data type..
http://help.sap.com/saphelp_nw70/helpdata/en/2d/c0633c3a892251e10000000a114084/frameset.htm
Thanks,
Vijaya.

Why do I get error -17500 when calling a batch file using the call executable step type?

I am calling a batch file using the call executable step type. If the path to the batch file contains a space I get error -17500 and a message stating there was an error in "Post". For example the path to the batch file is "c:\TestWin\Test Files\...\Program.bat" When I run this I get the above mentioned error, however if I change my directory structure so the path is now "c:\TestWin\TestFiles\...\Program.bat" it runs fine. I use the browse feature to find my batch file so it is not me typing in a path incorrectly. I have removed the batch file and I get a different error stating that it couldn't find the file so it appears that for my error it can find the file but can't run it. I am
sure that this has something to do with the fact that batch files are written in DOS but really don't want to resort to changing my directory structure on all my test stations. Is there any way to fix this problem so I can leave a space in my path?

It appears I have figured it out. This was on another computer so I was unaware of how they used their computer. I like you got it to work in the temp directory and in fact got the program.bat file to work as long as I put it under the temp directory, but when I switched out to my TestWin directory it wouldn't work, so I removed everything from the directory except the batch file it self and it work. What I found out after adding files in one at a time is that the person had a file called "Test" with no file extension in there "c:\TestWin\" directory. Removing this file made it work. Putting the file back broke it. So it appeares that when teststand was running it followed the path saw a space and attempted to grab the "Test" file instead of bro
wsing into the "Test Files" directory. If you create a file in your temp directory called "temp" with no file extension you will see the same problem. Thank you for your help.

User Decision step type

Hi,
I have developed a WF for 'Notification of Absence'. In this, a leave request is sent for approval.
When the leave request is Rejected, the creator has to make a decision (User Decision step type used) as to 'Withdraw' or 'Update' the request. But in the inbox of the creator, there is no option for "Withdraw' and 'Update'. What could be the reason for this? Am i missing something?
Thank you for your time.
Ajay

Hi AD,
are you trying to process anything else after the Decision Step in your WF definition ?
If yes, then what are you trying to process after it
If no, then try what JMB said, GUI problem, I doubt that but you can try as you need to resolve it.
Did you try removing the buffer ?
Hope it helps.
Aditya

Workflow-step type condition

hai all.....
I have got a problem while working with the step type 'condition' in workflow,i.e i want to check the values in internal table in my step type for example,whether the internal table is initial....please someone help me ..its very urgent...

Hi Kasi,
I can provide u a simple workaround for this...
U can create another table within the workflow container of the same table type.
name it as empty_<table>.
Than within the condition step, u can simply compare the original table with the dummy empty_<table>.
This should solve your issue
Regards,
Mahesh.

Step type 'condition' in workflow

hai all.....
I have got a problem while working with the step type 'condition' in workflow,i.e i want to check the values in internal table in my step type for example,whether the internal table is initial....please someone help me ..its very urgent...

Hi Kiran,
For the Operator 'NX' u need not enter any comparison value. U click on the condition in the condition step type . A window appears and u click on the internal table in expression 1 and the operator as 'NX' . It doesnt need a comparison value.
Now u check this with the test data in the same window . U will have an icon in the bottom of window to enter test data and another icon to evalutate it . U check it with data and without data. It will work .
In ur reply to Kasi , Ur answer is not at all related with what kasi asked for .U can check the initial property while the data is in workflow container itself . Instead u r passing the data from workflow container to task container and then to method container and then the processing has to take place in BO and again the reverse should take place .Which is Unnecessary .
Regards,
Scobby.
Be Free To Award Points

"Disable tracing" as part of custom step type behavior

Hi !
Currently writing custom step types based on sequences (my step type's default adapter is a sequence), I would like to set the "disable tracing" right in my step type definition.
The problem is that this option isn't visible in the 'Default Run Options" tab... The only way I found to do this is using Pre and Post Expression to set 'ThisContext.Tracing = True /False'.
But I don't like the fact to use Pre/Post Expressions in my step type (I would prefer to let it blank for end users).
Is there any way to achieve this without using Expressions ?
Solved!
Go to Solution.

Here a printscreen on the properties available for my custom step... No TS container...
Am I missing something ?
Attachments:
Step Prop.png ‏15 KB

Problem in Form step-type

Similar Messages

Maybe you are looking for