Databases
StackOverflow2013
Postsdbo
PORecommended Development practices for working with Siebel CRM?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORecommended Development practices for working with Siebel CRM?
    primarykey
    data
    text
    <p>I may be working with Siebel CRM soon, and I'm looking for advice on using modern development practices and enterprise best practices.</p> <p>Specifically I'd like advice on the following areas:</p> <ul> <li>How should we set up version control (specifically with Subversion)? What kind of structure should our repository have? How should we handle branches and tags?</li> <li>How can we do code reviews? How can we peer review configuration changes made through Siebel Tools that don't necessarily have any "code"? We want to review these changes for quality assurance and knowledge transfer, as well as compliance with change management policies.</li> <li>What sort of change management works well with Siebel? How do we verify that only things listed in our change log are actually changed when we do a new deploy?</li> <li>How can we automate testing of our application? Is unit testing even possible with Siebel? I saw another question suggesting QTP for web testing, but are there other options that work?</li> <li>Are there other things we can do to implement Continuous Integration practices with our Siebel development efforts?</li> <li>What recommendations do you have for naming conventions and other things that would traditionally fall under "coding style" guidelines?</li> <li>How should we separate development roles from Siebel Administrator roles? What should our build/test/deploy cycle look like?</li> </ul> <p>It's not likely that I'll be able to obtain any new expensive tools for this, but if there's a paid tool that provides really great ROI, feel free to mention it.</p> <p>If you have other recommendations along these lines, but not specifically addressed by one of my questions, feel free to add that as well.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USphicou
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORecommended Development practices for working with Siebel CRM?
      1. USAJPerez
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload