Form Object Default Curser on UPDATE, not working... ?

HighOnTek

Member
Hoping someone can identify what I'm missing, where I'm going wrong... or at the very least suggest an alternative so I can get the same desired results. :)

Using --> JDE Tools 9.1.4

My Problem:
When it comes to existing WO's, our users typically start editing the WO status as the Unit # will have already been selected when the WO was initially entered. They find it quiet frustrating that they start to edit the status, and the cursor jumps on them to the Unit Number field... often causing them to overwrite any existing text, then having to correct it when they've noticed the mouse cursor jumped on them.

What I'd Like:
Right now the default cursor for P13714 on ADD & UPDATE is set to 'Unit Number' field through its control option properties.
I would like to leave that property setting for ADD on unit # alone, so all new WO's being added will have the mouse cursor by default in that field just as it is today.
However for UPDATES, I'd like there either to be NO the default field, or to have the default changed to the 'Status' field.

What I've Tried:
Test 1:
I have unchecked the 'Default Cursor on update mode' control option for the WO unit number object in the hopes the cursor will just stay wherever our users put it in WO open, and not jump to a pre-defined default field.
Saved, Promoted my project into TEST and no change. The cursor still jumps to the Unit number field when I attempt to open and edit an existing WO.

Test 2:
I have unchecked the 'Default Cursor on update mode' control option for the WO unit number object, and checked the same control option on the WO status object in the hopes the default field would be the WO status, thus staying in the status field as that is the 1st field they begin to edit anyways for existing WO's.
Saved, Promoted my project into TEST and no change. The cursor still jumps to the Unit number field when I attempt to open and edit an existing WO.

Any help or feedback is appreciated,

HTK
 

Chan Rana

Legendary Poster
Also check on the tab sequence.

When you say prompted my project to Test i think you are building/deploying and then testing. Are you testing it on Web browser after the deployment?. Simple would be to make change on fat client and then test it on local web that way you can test quickly and check if the changes made any effect on screen.

Chan
 

HighOnTek

Member
Chan, that's exactly what I ended up doing...
My apologies, I'm relatively new to JDE Development and thought if I pushed my OMW Project to Status 26 it was deployed to our TEST environment... I learned recently though that this is not the case, it needs to be packaged and deployed by our CNC to hit the web servers.

I was not testing it locally, which I tested after learning that it would need to be packaged then deployed and it worked in my local.
So the property change does work, gave me the expected results without issue.

Thanks for the replies guys,

HTK
 
Top