Dates: | Jan 2018 - Sep 2018 | Role: | Siebel Developer |
---|---|---|---|
Location: | UK | Software: | Siebel Financial Services 8.1.1.11 OUI (IP13) |
Skills: | General configuration, OUI, workflow, scripting, EAI, html, JavaScript, jQuery, Agile. | ||
Summary: | Mark joined this well-established Agile project as a development resource for ongoing updates and 3rd level support. | ||
Detailed Description | |||
The Christie’s Siebel implementation was a well established implementation that had been in place for many years. Mark was primarily brought in to apply updates required for the upcoming GDPR changes which required basic configuration changes as well as some interface changes and complex OpenUI modifications. As part of the GDPR changes Christie’s wanted to introduce a number of marketing preferences. It was decided that the best way to present these preferences was via a grid of radio buttons. Unfortunately, the standard Siebel radio button did not work in Christie’s version of Siebel (8.1.1.11 IP13), with multiple issues including the incorrect focus when tabbing through radio controls, read only state not being applied, and the selected button not being refreshed when the underlying record changes. Although Siebel had apparently resolved these issues in later versions there was no scope to upgrade the version of Siebel used by Christie’s, so Mark was able to use OpenUI to modify the radio controls generated by Siebel such that they worked as they should. Other OpenUI configuration included highlighting rows in a list applet with a specific field value, adding the red asterisk that indicated a required field to the label on list applets (this would automatically be applied to all list applets throughout the application), modifying the layout of certain controls on specific applets, changing the confirmation message presented by Siebel when deleting a record in a many-to-many relationship. Apart from other general configuration and minor bug fixes, Mark also worked on a number of interfaces, including some to support a web portal application that provided users with a news feed on their key customers. These interfaces involved web services as well as stored procedures in the database. |