Who's Online Now
0 registered members (), 6 guests, and 16 spiders.
Key: Admin, Global Mod, Mod
Newest Members
vjnanda, NickyB, AKR, Barry_Test_User, KVS
1286 Registered Users
Recent Posts
Top Posters(30 Days)
Popular Topics(Views)
481,388 PAYE RTI
57,620 HR_PF.K RUP4
Previous Thread
Next Thread
Print Thread
Rate This Thread
#12133 - 14/04/18 01:21 PM Assignment Category Validation  
Joined: Jan 2013
Posts: 17
Sandy Offline
Sandy  Offline

Joined: Jan 2013
Posts: 17

I have got a requirement to restrict the updation of Assignment Category from ‘Contract’ to ‘Employee’ and vice versa.
Customer is having many interfaces also. We need to restrict the updation both from the GUI as well as interfaces.

GUI could be restricted through Form Personalization. Is there any way to put this restriction irrespective of any mode
i.e. through GUI and interfaces.

Thanks !!

#12134 - 16/04/18 11:23 AM Re: Assignment Category Validation [Re: Sandy]  
Joined: Jun 2005
Posts: 254
pat Offline
claiming squatters rights
pat  Offline
claiming squatters rights

Joined: Jun 2005
Posts: 254
Hardy's Way
Hi Sandy,

If all three methods are calling the public api then your developers may be able to add a "before update" user hook to the api to raise an error if the transaction fails validation.

Beware. I'm a Functional Consultant so you should get this confirmed by a Techie - who will probably suggest a better alternative!


#12141 - 07/05/18 02:53 PM Re: Assignment Category Validation [Re: Sandy]  
Joined: Mar 2005
Posts: 2,103
CT Offline
CT  Offline


Joined: Mar 2005
Posts: 2,103
I used to be a techie... A before user hook would certainly allow the rule to be applied where the transaction was initiated via the standard API.


It always used to be that professional user forms did their own thing in respect of managing updates to the base table (e.g. assignments screen manages changes to assignment rows) - that is to say, they didn't use the API! There is a somewhat lame reason behind this which I will not bore you with, but as far as I am aware the functionality had not changed that much in R12.2.

The upshot of which is, you'll need to apply the same validation logic to the Forms Personalisation also. Having said that, if you set it all up in its own package procedure/function, and then called the same code from user hook and forms personalisation, that will at least allow you to make the rule more manageable in the event of the need to alter it in some way.

Hope this helps.



#12143 - 08/05/18 05:30 AM Re: Assignment Category Validation [Re: CT]  
Joined: Mar 2005
Posts: 1,297
delboy Offline
The Grand Daddy
delboy  Offline
The Grand Daddy

Joined: Mar 2005
Posts: 1,297
Somewhere in South of England
Originally Posted by CT
I used to be a techie...

CT, once a Techie, always a Techie!!

Moderated by  Administrator, Geoff Dixon 

Forum Statistics
Most Online90
Mar 5th, 2017
Today's Birthdays
No Birthdays
Recent vacancies
Top Posters(All Time)
CT 2,103
delboy 1,297
bcooper 1,291
paulgos 436
SBi 426
pat 254
Gus 252
vkumar 223
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
Powered by UBB.threads™ PHP Forum Software 7.6.0
Page Time: 0.027s Queries: 15 (0.009s) Memory: 2.7551 MB (Peak: 2.9099 MB) Zlib disabled. Server Time: 2019-06-27 08:20:11 UTC