Siebel Composer



here I have two applications Siebel web tools and Siebel a communications let's log into the applications as we log into the applications the Siebel web tools applications will look very familiar and very similar to Siebel tools especially as we open up the first level navigation here the objects that are visible here are more or less the same as the objects that are that are available in Siebel tools in the object Explorer the way we configure each one of these objects remain almost the same except that we are now running in a web-based environment so let's let's look at some of these screens here applet application business component and so on and so forth are all configurable object in the Indus evil application there are a couple of additional screen here that we will get to shortly let's go into the e-communications application this application at this point looks far too similar to what we've shipped in IP 2014 or even in IP 2015 where the applications structure layout formatting configuration even navigation remains intact and views that we are very familiar with in the Siebel application in the Siebel e-communications out-of-the-box application remain intact including all aspects of the application the big difference in this application versus everything that we have seen so far is that this application is running by reading the repository configuration and the web template information from a runtime metadata and as its as we see here in the apart about repository pop-up it is actually running on top of runtime metadata version 8 it is not reading a file at this point so the entire application is running with metadata that's residing in the runtime tables which is something new we've introduced with SIBO composer now as we just saw here the navigation look and feel of the application remains almost the same as far as the demo scenario is concerned we're gonna go ahead and make a few changes here so we're gonna go and change the oracle logo in the account list view we're gonna drop the account form applet for tablet we're gonna in place of the account format let's show a contactless tablet and within the account list after itself we will drop a few columns here for tablet and for phone and we will also inactivate this last column here called fun eligible or hide it for all resolutions essentially a global height and we will also change the label of the status column here which currently shows status to show a different label and in this particular case we're gonna just pick TOI status let's go ahead and make those changes we leave this application running as this so here let's start with the top-level entity and we want to change the application logo so we will start by going into web template which is where the logo information is defined you will find the web template information all the specific web quickly that we want to make a change for and here we will look for the actual entry and this is this is something new that we've introduced with composer mode where web template data is now displayed in our Siebel web tools application where the HTML structure is now transformed on migrated into metadata as list of rows that we can manipulate and modify so here we have a specific element which holds the class name that is used to render the oracle logo and we'll simply go ahead and append another class another pre-configured class name called c UI open world logo and this simple change is sufficient to trigger the logo to change in the application at this point this version has not been published so even though I've made a change the application remains unchanged because I still have the changes are committed locally but not published yet to the runtime tables so I just went ahead and made a change and this this one change is sufficient to go to change this logo to a pre-configured open world logo next we will go into the view entity and query our account list view and here we have one web template and multiple applets defined here notice that my account there are a couple of applets that are grid that are actually read-only and right here you will see that the account entry applet and the contact list applet out of inactive I've made some changes here ahead of time for the demo where I've configured expressions to indicate the resolution in which I want the applet to show or hide so here in this particular case I've configured the account entry applet to show four resolutions greater than that of a tablet and and the end to show the contact list applet for resolution that is less than that of desktop so so essentially if they are mutually exclusive so I'm gonna go ahead and active activate this applet so that the change that I've made here takes effect and that's about all I had to do so addition of these expressions and then enact activating the corresponding record was pretty much all I had to do for this change to take effect now I'm gonna go into the next level of granularity where I go into an applet and in that in the account list applet so let's go ahead and query for that in the account list applet we have a set of list controls that we have defined but what we want to do is we want to change the changed what columns displayed for what type of resolutions so we'll go ahead into the applet web template entity and here edit list is the web template that is exposed by default so let's go ahead and look at some of the changes that I've already made ahead of time but not yet published so in this particular case I've added similar expressions to each one of these columns here so for account status I've had an expression here at the at the very end to say that this column need should be this should be displayed only when the resolution is greater than that of a phone so it'll show up for a tablet and for a desktop fund eligible flag is something that I want to actually inactivate so I'm going to go ahead and make a change here to change the value from active to inactive and the location column which is essentially the site column it will be displayed only for resolution greater than none of our tablets only for desktop and similarly for the account name and for the other columns here as well for sales rep and for type this is again configured to be hidden in a form so these these expressions are the ones that we had to add to drop off columns at various screen resolutions as I mentioned earlier Siebel web tools is a like-for-like exposure of Siebel tools in an open UI based application now we've gone ahead and done the changes at the applet web template level and we're going to make two more changes one at the lists control level where we will change the status label from status which is what is configured right now to TOI status I'm gonna go ahead and create an override so that the column label changes from status which is what it is right now to TOI status which is what I – here in the list column let's call them local overrides so we have done all the changes that that we planned to do change the logo change the applets that are displayed in the various UI resolutions and in the applet drop columns for tablet and phone and then at the at the control level change the label of a specific control now that we have done the changes these these changes have not taken effect yet and how we howdy how we publish them to take effect is to go into this new screen called administration runtime configuration where it will list all the objects that we just modified so it actually kept track of all the changes that we modified and it's listing that here by saying we modified a web template this was for the logo and the operation was an update we modified a view this was for dropping and sorry hiding and showing applets in specific resolutions and then the applet both to change the label of controls and to also do the responsive web design part where we'll be dropping columns for specific screen resolutions I can also go into this other view called published versions which actually keeps track of all the versions that have been published if you recall we had seen that the a communications application was running on metadata version over 8 which is what this this is right now which is the active version so let's go ahead to the publisher view and go ahead and publish all these changes to take effect right away now when when this publish happens it is actually using the standard compilation process but instead of writing the compilation to a file it's actually writing that to the runtime tables and by that we have already published the change the the list is now empty so it actually successfully compiled the changes and we can verify that by going into the published versions view where we will see that version 8 which was active is now inactive and version 9 which is which has the changes that we made in these three entities is now the active version however if we switch back to the e-communications application which is what we were looking at earlier this application is still using version 8 and this is because the metadata that the application requires per session is is cached at the time of login so while I'm logged in even if a new version gets published I'm still using the same version that was that was cached for me at the time of login so as I navigate through the various views I'm still using version 8 of the metadata and we can verify that by going in here again and looking at up about repository for me to take version 9 and run that in the application all I need to do is log out and log back in we don't need a server restart because we don't have any files to read or files to update so a simple log out and log back in into the application will force the application to read metadata version number 9 and cache that for that session so every new user that logs out or creates a new session by logging in will get metadata version 9 here we are the block will be logged out and log back into the application and you already noticed that my logo has changed from the original Oracle logo to the Oracle OpenWorld logo so one change has already taken effect and we can verify that we are running version 9 by going into a Power repository and you'll now see that my metadata version 9 is active let's look at a couple of other changes that we made along the way so we went into the account list view and for the most part we wouldn't see any changes here because all the responsiveness or the all the expressions that we added were for tablet and phone resolution but we will see two changes one is the fund eligible column which was my last column here is no longer it's no longer my last column it is account team which was the last part one column which means that the inactivated fund eligible column is now not visible and the status label that we had changed from status to TOI status has now taken effect so two changes that we made globally regardless of resolution have already taken effect in my desktop version of the application now what I'm gonna do is I'm gonna bring up my iPad and do the same login to the exact same application using using a physical device so I'm gonna login to the application and I'm um the iPad is also connecting to the same application version that we are connected to in the desktop on the background here and when we log in you will see the client-side responsiveness which we made available an IP 2014 already kick in where some of the some of the differences like the actual logo not displaying the file edit view menu not displaying the buttons being larger all of those things have already kicked in by default the client side and the service our responsiveness work hand-in-hand now we're going to go in here and go into the account view and drill into the account list view and as we do this we will notice a difference right there we will notice two differences one is if I move if I move this down a little bit you'll notice that the number of columns in the account listed on the top here are different from the number of columns displayed here so we have named account main phone number account class site is no longer available parent is no longer available tôi status is now available account type is available but account team has been dropped so the three columns that we decided that we configure to drop for a tablet resolution has been dropped off the payload itself so the payload that the iPad is getting from the server when this Apple is requested is lighter than if the same app it was requested in by a desktop environment so the payload the payload and the network through a network traffic is fine to you depending on which device is asking for the same configuration now not only do we see that change in the number of drop columns but you'll notice the applet at the bottom is no longer an account for Maplin it is indeed a contact list app but which is what we configure it to configure it to be we configure it such that the account form applet would drop off for tablet resolution and it would be replaced by a contactless tablet in a tablet tablet resolution so the same application same view has different look and feel different behavior different payload different functionality on different devices based on the device that requests in it will take it a step further and we will pull up a form form factor so here I have a browser window that I've resized to a form a phone form factor pointing to the same application and I'm going to log in here as well and when we log into this application we will notice that the same changes that I have that have to affected the global changes that have affected the desktop versus tablet versus phone are all taking effect in the same place however we will see some additional changes here so we will see that because this is running in the phone form factor further columns have been dropped so new name remain intact main phone remain intact however account account class remains intact also however tôi status and account type have been dropped in the phone resolution and the car the contact listed which was swapped for the account for map it also shows up in a phone fight or phone form factor so as you can see here one application one view multiple form factors gave different behavior and not only is it is it different in behavior but it is all done through a single unified tool

One Reply to “Siebel Composer”

Leave a Comment

Your email address will not be published. Required fields are marked *