Peoplesoft : making pushbutton required through peoplecode

Question

1.00/5 (1 vote)

See more:

Can someone please tell me the code for the following scenario.

Say I have two fields and a push button on a page(standard page)
Field1 : A(required)
Field2 : B
A pushbutton related to field B

The pushbutton has the magnifying glass symbol. Clicking upon the pushbutton takes me to the secondary page. Upon clicking 'OK' on secondary page, the outcome of the secondary page is given to the field B of standard page.

In the record field fieldchange event for pushbutton,
The following is the logic written.
Upon saving the standard page, if field B is empty, the value of field A gets saved into value of B.

If field B is given value, the value of A (concatenation) B gets saved into field B.

If field B value Is given from secondary page, the value of A (concatenation) secondary page value gets saved into field B.

But the requirement here is, the page should not get saved until the values of the secondary page is given. I.e.. the push button should be made 'required'.

What is the best way to achieve this? Piece of code to achieve this would be helpful.
Have tried putting record.Field.showrequiredfieldque=true in the record-field fieldchange event doesn't help.

Any suggestions on this please?

What I have tried:

Have tried putting record.Field.showrequiredfieldque=true in the record-field fieldchange event doesn't help.

Posted 27-Jun-16 5:08am

PSnewbie

Updated 22-Feb-19 15:57pm

Blutfaust

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Member 14159889 · Answer 1 · 2019-02-22T15:58:00

I would try adding a custom char field that is unrelated to the button and set the field in the record definition to required and that will keep the user from being able to save the page with out supplying the field with a value. So how does that help? Simple, hide the field and have the PeopleCode tie to the Required Push Button place a value in the new custom required field. Make sure to leave the default value attribute blank for the field and I suggest placing post-save code to delete the value so the field is usable again if the user selects the same dataset again from scratch.

That might work.