One method to add security data for your integrating application is to use a procedure that is run after the system administrator successfully logs into Microsoft Dynamics GP. The following example is a portion of the Startup procedure for the sample integrating application. It registers a procedure trigger that is activated when a user successfully logs into Microsoft Dynamics GP.
local integer l_result; l_result = Trigger_RegisterProcedure(script Add_Successful_Login_Record, TRIGGER_AFTER_ORIGINAL, script IG_CreateSecurityData); if l_result <> SY_NOERR then warning "Procedure trigger for adding security data failed."; end if;
In the trigger processing procedure, the security tasks, security task operations, and security roles for the integrating application are created.
The reports available in the various security setup windows in Microsoft Dynamics GP are a good way to verify that the security data for your integrating application has been installed correctly.