Siebel - Terminating/blocking user from Siebel application without changing LOGIN ID

 

We change Login ID most of time when we need to block or terminate user from Siebel application. Whereas we can achieve this by configurations as well. In Vanilla Siebel we have field called as "Employment Status", by leveraging this field and using small configuration we can have more granular reason of blocking or termination of account.

To achieve this I have exposed this field on "Employee List More Info View" view as below.

Secondly I have added this field into "Login User" business component along with Search specification as [Employment Status]='Active' . Details are as below

With Employement Status as "Active", I was able to access Siebel properly whereas when change was made to other than "Active" got error message as below.

Note:- Please make sure that SADMIN, other proxy account and integration accounts are set to “Active” before rolling out new change.

Salesforce – Apex DataLoader and Automated migration interface

 

Scenario :- We wanted to build the automated Employee interface which will create/update/terminate User inside Salesforce when changes are done in Organizational HRMS.

 

To build we have following options -

• Use Apex Dataloader
• Build Standalong Java apps and use Salesforce Webservices
• Use of other tools like Apatar, OnDemandInformation etc.

Based on License/development cost and scalability we decided to use Apex Dataloader. If you wanted to use Apex data loader then either you can use the lastRun date to find out which records to interface or stamp status back to source data (Database table). If you decide to stamp status back to source data then dataloader does not provide the functionality to do that (atleast I am not aware :-) ). To achieve we wrote small java program which will use success file and error files generated by loader and will update the source database table.

Here is high level flow.

Flow:-
First run the data loader using configuration
once completed call java program with appropriate connection parameter and log file location. Java program will update the source records as success if found in success file and error if found in error file.

Enjoy :)