<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Yener Ipeksac on Medium]]></title>
        <description><![CDATA[Stories by Yener Ipeksac on Medium]]></description>
        <link>https://medium.com/@yener.ipeksac?source=rss-25ac4f22d17d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RMTkoAbke-T_-YxUBsBTow.jpeg</url>
            <title>Stories by Yener Ipeksac on Medium</title>
            <link>https://medium.com/@yener.ipeksac?source=rss-25ac4f22d17d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:42:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yener.ipeksac/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Creating a Custom Dashboard in Siebel 22.3 Using HTML, CSS, and JavaScript]]></title>
            <link>https://medium.com/@yener.ipeksac/creating-a-custom-dashboard-in-siebel-22-3-using-html-css-and-javascript-381817a9c792?source=rss-25ac4f22d17d------2</link>
            <guid isPermaLink="false">https://medium.com/p/381817a9c792</guid>
            <category><![CDATA[siebel]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[dashboard]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[html]]></category>
            <dc:creator><![CDATA[Yener Ipeksac]]></dc:creator>
            <pubDate>Tue, 04 Mar 2025 08:33:50 GMT</pubDate>
            <atom:updated>2025-03-04T09:06:01.309Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>In Siebel 22.3, customizing the user experience is essential for improving usability and efficiency. One of the ways to achieve this is by integrating a custom dashboard directly into the Siebel web interface. In this article, we will walk through how we built a custom dashboard using HTML, CSS, and JavaScript, directly modifying the Siebel Web Template. This dashboard displays key metrics and charts, providing users with real-time insights.</p><h3>Why a Custom Dashboard?</h3><p>By embedding a custom dashboard, we can:</p><ul><li>Improve UI aesthetics with modern design elements</li><li>Increase interactivity with real-time updates</li><li>Enhance visibility of key performance indicators (KPIs)</li><li>Provide a seamless integration within Siebel</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iEFK5a--BKuXFVcKPQbu2w.png" /></figure><h3>Implementation</h3><p>To create the custom dashboard, we structured the interface using HTML and CSS while integrating JavaScript for data handling and rendering charts dynamically. The core steps include:</p><ol><li><strong>Modifying the Siebel Web Template</strong></li><li><strong>Designing the Layout with HTML &amp; CSS</strong></li><li><strong>Fetching and Updating Data from Siebel Business Services</strong></li><li><strong>Implementing Interactive Charts using JavaScript</strong></li></ol><h3>HTML Structure</h3><p>The dashboard contains several sections, including KPI cards, filters, and visual charts. Below is the core structure of the dashboard:</p><pre>&lt;div class=&quot;dashboard&quot;&gt;<br>    &lt;div class=&quot;card&quot;&gt;<br>        &lt;h3&gt;₺ Open Opportunities (Count)&lt;/h3&gt;<br>        &lt;p class=&quot;highlight&quot; id=&quot;openOppty&quot;&gt;0&lt;/p&gt;<br>    &lt;/div&gt;<br>    &lt;div class=&quot;card&quot;&gt;<br>        &lt;h3&gt;₺ Open Opportunities (TL)&lt;/h3&gt;<br>        &lt;p class=&quot;highlight green&quot; id=&quot;openOpptyTL&quot;&gt;0₺&lt;/p&gt;<br>    &lt;/div&gt;<br>    &lt;div class=&quot;card&quot;&gt;<br>        &lt;h3&gt;My Opportunities (2025 - Count)&lt;/h3&gt;<br>        &lt;p class=&quot;highlight&quot; id=&quot;totalOpportunities&quot;&gt;0&lt;/p&gt;<br>    &lt;/div&gt;<br>&lt;/div&gt;</pre><h3>CSS Styling</h3><p>To improve UI aesthetics, we used modern CSS styling:</p><pre>.dashboard {<br>    display: flex;<br>    justify-content: space-around;<br>    padding: 20px;<br>    background-color: #fff;<br>    box-shadow: 0 4px 8px rgba(0, 0, 0, 0.1);<br>}<br>.card {<br>    flex: 1;<br>    margin: 0 10px;<br>    padding: 20px;<br>    border: 1px solid #ddd;<br>    border-radius: 5px;<br>    background-color: #fff;<br>    text-align: center;<br>    box-shadow: 0 2px 4px rgba(0, 0, 0, 0.1);<br>}</pre><h3>Fetching Data from Siebel</h3><p>To integrate with Siebel data, we used Siebel Business Services:</p><pre>function callSiebelBusinessService(serviceName, methodName, inputs, callback) {<br>    try {<br>        var svc = SiebelApp.S_App.GetService(serviceName);<br>        var psIn = SiebelApp.S_App.NewPropertySet();<br>        for (var key in inputs) {<br>            psIn.SetProperty(key, inputs[key]);<br>        }<br>        var psOut = svc.InvokeMethod(methodName, psIn);<br>        callback(psOut);<br>    } catch (e) {<br>        console.error(&quot;Siebel connection error&quot;);<br>    }<br>}</pre><h3>Rendering Charts</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RIbfQG4kfSoQbcv8lly7Bw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dXxBBgw0-c15kGcc1H4EQQ.png" /></figure><p>To visualize data, we used the HTML5 Canvas API and JavaScript:</p><pre>function createChart(ctx, data, labels) {<br>    new Chart(ctx, {<br>        type: &#39;bar&#39;,<br>        data: {<br>            labels: labels,<br>            datasets: [{<br>                data: data,<br>                backgroundColor: [&#39;#1e90ff&#39;, &#39;#28a745&#39;, &#39;#dc3545&#39;, &#39;#ff7f00&#39;],<br>            }]<br>        }<br>    });<br>}</pre><h3>Key Learnings &amp; Considerations</h3><ul><li><strong>Data Retrieval:</strong> Fetching real-time data from Siebel requires careful integration with Business Services.</li><li><strong>Performance Optimization:</strong> Using efficient JavaScript techniques ensures smooth UI performance.</li><li><strong>UI Design:</strong> A clean and modern interface significantly improves user experience.</li></ul><h3>Conclusion</h3><p>Custom dashboards in Siebel 22.3 provide enhanced flexibility and user experience. By leveraging HTML, CSS, and JavaScript, we were able to build a real-time, interactive, and visually appealing dashboard.</p><h3>Next Steps</h3><ul><li>Extend functionality with additional filtering options.</li><li>Implement drill-down capabilities for deeper data analysis.</li><li>Optimize performance for large datasets.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=381817a9c792" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Siebel Custom Calendar Development]]></title>
            <link>https://medium.com/@yener.ipeksac/siebel-custom-calendar-development-8061fcb5e4f3?source=rss-25ac4f22d17d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8061fcb5e4f3</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[html]]></category>
            <category><![CDATA[siebel]]></category>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[css]]></category>
            <dc:creator><![CDATA[Yener Ipeksac]]></dc:creator>
            <pubDate>Fri, 07 Feb 2025 14:29:48 GMT</pubDate>
            <atom:updated>2025-02-07T14:29:48.355Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*-L58KedevgQ8g2Jr0oB60A.png" /></figure><h3>Introduction</h3><p>In Siebel CRM version 22.3, we developed a custom calendar application to enhance customer management processes. This customized calendar allows users to view opportunities, activities, and competitor information on specific dates directly from the Siebel interface. Users can navigate to relevant records or create new entries seamlessly.</p><p>This article explains how the custom calendar was integrated into the Siebel Web Template using HTML, CSS, and JavaScript.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MuBJ1wqSmb1MW9WF" /></figure><h3>Requirements</h3><p>The custom calendar fulfills the following requirements:</p><ul><li><strong>Display date-based opportunities, activities, and competitor information</strong></li><li><strong>Provide direct navigation to relevant opportunities, activities, or competitor records</strong></li><li><strong>Enable new record creation and navigation to the respective screens</strong></li><li><strong>Allow month-to-month navigation</strong></li><li><strong>Include a “Go to Today” button for quick access</strong></li></ul><h3>Technologies Used</h3><ul><li><strong>HTML5</strong>: To structure the calendar interface</li><li><strong>CSS3</strong>: For styling and creating a modern, user-friendly design</li><li><strong>JavaScript</strong>: To fetch data from Siebel and enable interaction with the calendar</li><li><strong>Siebel Business Service (BS) Integration</strong>: To retrieve data and manage user interactions</li></ul><h3>Calendar Components</h3><p>The calendar interface consists of the following components:</p><ul><li><strong>Calendar container</strong>: The main structure that holds all calendar elements</li><li><strong>Month and year header</strong>: Displays the current month and year</li><li><strong>Weekday labels</strong>: Represents the days of the week</li><li><strong>Date cells</strong>: Displays information on specific dates, highlighting those with associated data</li><li><strong>Modal window</strong>: Shows detailed information when a user clicks on a specific date</li></ul><h3>Development Process</h3><h3>1. HTML Structure for the Calendar</h3><p>The calendar is dynamically updated using the following HTML structure:</p><pre>&lt;div class=&quot;calendar&quot;&gt;<br>   &lt;div class=&quot;month&quot;&gt;<br>      &lt;button id=&quot;prevMonth&quot;&gt;&amp;#10094;&lt;/button&gt;<br>      &lt;h2 id=&quot;monthYear&quot;&gt;&lt;/h2&gt;<br>      &lt;div style=&quot;display: flex; align-items: center;&quot;&gt;<br>         &lt;button id=&quot;goToToday&quot;&gt;Go to Today&lt;/button&gt;<br>         &lt;button id=&quot;nextMonth&quot;&gt;&amp;#10095;&lt;/button&gt;<br>      &lt;/div&gt;<br>   &lt;/div&gt;<br>   &lt;div class=&quot;weekdays&quot;&gt;<br>      &lt;div&gt;SUNDAY&lt;/div&gt;<br>      &lt;div&gt;MONDAY&lt;/div&gt;<br>      &lt;div&gt;TUESDAY&lt;/div&gt;<br>      &lt;div&gt;WEDNESDAY&lt;/div&gt;<br>      &lt;div&gt;THURSDAY&lt;/div&gt;<br>      &lt;div&gt;FRIDAY&lt;/div&gt;<br>      &lt;div&gt;SATURDAY&lt;/div&gt;<br>   &lt;/div&gt;<br>   &lt;div class=&quot;days&quot; id=&quot;calendarDays&quot;&gt;&lt;/div&gt;<br>&lt;/div&gt;</pre><h3>2. Styling with CSS</h3><p>Modern and user-friendly styles were implemented with CSS, such as gradient backgrounds, hover effects, and emphasis on the current day.</p><p>Example of highlighting the current day:</p><pre>.today {<br>    background-color: rgba(255, 255, 255, 0.3) !important;<br>    color: #FFF;<br>    font-weight: bold;<br>    transform: scale(1.05);<br>}</pre><h3>3. JavaScript for Calendar Functionality</h3><p>JavaScript handles dynamic calendar generation and user interactions, including data retrieval from Siebel.</p><ul><li><strong>Initialization and Update Function:</strong></li></ul><pre>function initializeCalendar() {<br>    if (!calendarApp.initialized) {<br>        calendarApp.initialized = true;<br>        fetchOrganizations();<br>        attachEventListeners();<br>        refreshCalendarData();<br>    }<br>}</pre><ul><li><strong>Fetching Opportunities from Siebel:</strong></li></ul><pre>function fetchOpportunities(callback) {<br>    callSiebelBusinessService(&quot;TTG_SFA_Calendar_Operations&quot;, &quot;GetOpportunity&quot;, {<br>        &quot;StartDate&quot;: startDate,<br>        &quot;EndDate&quot;: endDate<br>    }, function(response) {<br>        if (!response) {<br>            console.error(&quot;Business Service response is empty&quot;);<br>            if (callback) callback();<br>            return;<br>        }<br>        calendarApp.opportunities = {};<br>        var opportunityList = response.GetChild(0).GetChild(0);<br>        for (var i = 0; i &lt; opportunityList.GetChildCount(); i++) {<br>            var opp = opportunityList.GetChild(i);<br>            var oppDate = formatDateToYYYYMMDD(opp.GetProperty(&quot;Date&quot;));<br>            var oppName = opp.GetProperty(&quot;Name&quot;);<br>            var oppDetails = opp.GetProperty(&quot;Details&quot;);<br>            if (!calendarApp.opportunities[oppDate]) {<br>                            calendarApp.opportunities[oppDate] = [];<br>                        }<br>                        calendarApp.opportunities[oppDate].push({<br>                            name: oppName,<br>                            details: oppDetails<br>                        });<br>                    }<br>                    if (callback) callback();<br>                });<br>            }</pre><h3>4. Displaying Opportunities, Activities, and Competitor Information</h3><p>To display data for specific dates, the following code adds event information to calendar cells:</p><pre>if (calendarApp.opportunities[dateKey] || calendarApp.activities[dateKey] || calendarApp.competitors[dateKey]) {<br>    const eventCount = document.createElement(&quot;div&quot;);<br>    eventCount.className = &quot;event-count&quot;;<br>    eventCount.innerHTML = `Opportunities: ${calendarApp.opportunities[dateKey].length}&lt;br&gt;`;<br>    day.appendChild(eventCount);<br>}</pre><h3>5. User Interactions</h3><ul><li><strong>Modal for detailed information</strong></li><li><strong>Options to create new opportunities, activities, or competitor records</strong></li><li><strong>Direct navigation to records</strong></li></ul><h3>Key Points</h3><ul><li><strong>Error handling</strong> during Siebel Business Service integration</li><li><strong>Date formatting</strong> to ensure compatibility with Siebel</li><li><strong>Asynchronous loading</strong> of organizations for better performance</li></ul><h3>Conclusion</h3><p>This development provides a dynamic calendar in Siebel that enables users to efficiently manage opportunities, activities, and competitor information. The enhanced visualization and seamless navigation contribute to better decision-making and streamlined business processes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8061fcb5e4f3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Optimizing Workspace Alignment in Siebel 22.3 with Python Script]]></title>
            <link>https://medium.com/@yener.ipeksac/optimizing-workspace-alignment-in-siebel-22-3-with-python-script-a16aeab8d13a?source=rss-25ac4f22d17d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a16aeab8d13a</guid>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[rest-api]]></category>
            <category><![CDATA[siebel]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Yener Ipeksac]]></dc:creator>
            <pubDate>Tue, 03 Sep 2024 06:46:11 GMT</pubDate>
            <atom:updated>2024-09-03T06:46:11.531Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/730/1*y9NuB8ny5GgJseTr9ZmGsw.png" /></figure><p>In the fast-paced world of enterprise applications, optimizing efficiency is always a top priority. One of the challenges faced within the Siebel 22.3 environment was the absence of a dedicated REST API service for workspace alignment. To address this, a custom Python script was developed that has drastically reduced the time needed for aligning workspaces, transforming what was once a lengthy task into a quick and seamless process.</p><p><strong>The Challenge</strong></p><p>Siebel 22.3 includes a comprehensive set of REST API services that support a broad range of functionalities. However, it lacks a specific REST API service for workspace alignment. This presented a significant hurdle, as manually aligning workspaces was not only time-consuming but also prone to errors.</p><p><strong>The Solution</strong></p><p>To overcome this gap, a Python script was created to automate the alignment process between two Siebel workspaces. The script interacts with the Siebel REST API, retrieves the necessary data from an Oracle database, and handles the alignment with minimal need for manual input. The script is designed to work with various object types and their relationships, ensuring that everything aligns accurately and thoroughly.</p><p>To further enhance efficiency, the script is integrated with Jenkins, allowing it to run automatically at scheduled intervals or in response to specific triggers. This setup ensures that workspace alignment is consistently maintained without requiring manual initiation.</p><p><strong>Key Components of the Script</strong></p><p>The script is quite detailed, but here are some of the critical components that highlight how it achieves automation:</p><p><strong>Database Connection and Workspace Identification</strong></p><p>The script starts by connecting to the Oracle database to gather the necessary workspace details. This step is crucial for identifying the specific workspaces and their version information.</p><p>connection = oracledb.connect(</p><p>user=”USER”,</p><p>password=”PASSWORD”,</p><p>dsn=”DB_HOST:PORT/SERVICE_NAME”</p><p>)</p><p>Using SQL queries, the script then pulls the workspace ID and version details needed for alignment.</p><p><strong>REST API Interaction</strong></p><p>The heart of the script is its interaction with the Siebel REST API, which it uses to retrieve data from the source workspace and apply it to the target workspace.</p><p>source_url = “https://USERNAME:PASSWORD@SIEBEL_SERVER/siebel/v1.0/workspace/&quot; + source_workspace</p><p>target_url = “https://USERNAME:PASSWORD@SIEBEL_SERVER/siebel/v1.0/workspace/&quot; + target_workspace</p><p>response = session.get(source_url, headers=headers, verify=False)</p><p>if response.status_code == 200:</p><p>data = response.json()</p><p>session.put(target_url, headers=headers, json=data, verify=False)</p><p>This segment of the script ensures that all necessary objects and their child objects are properly aligned between the workspaces.</p><p><strong>Handling Object Hierarchies</strong></p><p>Managing object hierarchies is a critical aspect of workspace alignment. The script systematically iterates through parent and child objects, recursively aligning each layer to ensure complete synchronization.</p><p>for item in items:</p><p>name = item[‘Name’]</p><p>source_url = source_url + “/” + name + “/” + child_type_name</p><p>target_url = target_url + “/” + name + “/” + child_type_name</p><p>response = session.get(source_url, headers=headers, verify=False)</p><p>if response.status_code == 200:</p><p>data = response.json()</p><p>session.put(target_url, headers=headers, json=data, verify=False)</p><p>This recursive approach guarantees that all related objects are aligned correctly, preserving the integrity of the workspace.</p><p><strong>Final Notification</strong></p><p>Once the alignment is successfully completed, the script sends a notification via Microsoft Teams, confirming that the workspaces have been aligned.</p><p>my_teams_message.text(source_workspace + “ workspace has been successfully aligned with “ + target_workspace)</p><p>my_teams_message.send()</p><p><strong>Results</strong></p><p>The implementation of this script, coupled with its integration into Jenkins, has reduced the time required for workspace alignment from hours to mere minutes. This automation not only saves time but also minimizes the potential for human error that comes with manual processes. The success of this script highlights the power of custom automation in extending the capabilities of Siebel, particularly in areas where standard solutions fall short.</p><p><strong>Conclusion</strong></p><p>While Siebel 22.3 may not provide a built-in REST API for workspace alignment, with the right tools and a bit of creativity, it’s possible to bridge this gap. This custom Python script, combined with Jenkins automation, underscores the value of such integrations in enhancing both the efficiency and reliability of enterprise systems.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a16aeab8d13a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automating SSL Certificate Renewal for Siebel on OpenShift using GitLab]]></title>
            <link>https://medium.com/@yener.ipeksac/automating-ssl-certificate-renewal-for-siebel-on-openshift-using-gitlab-4c8e79c20166?source=rss-25ac4f22d17d------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c8e79c20166</guid>
            <category><![CDATA[powershell]]></category>
            <category><![CDATA[siebel]]></category>
            <category><![CDATA[openshift]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[gitlab]]></category>
            <dc:creator><![CDATA[Yener Ipeksac]]></dc:creator>
            <pubDate>Mon, 02 Sep 2024 06:47:23 GMT</pubDate>
            <atom:updated>2024-09-02T06:51:02.556Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*QIFhnADkXLmRoJeQuGITsg.png" /></figure><h3>Introduction</h3><p>As a Siebel Developer working with version 22.3, I recently encountered the challenge of automating the SSL certificate renewal process on our OpenShift environment. The SSL certificates used on our Siebel application’s OpenShift routes require annual renewal — a task that, until now, involved a manual and often cumbersome process. Despite having a user manual in place, the lack of hands-on experience with the process made it challenging for those unfamiliar with the procedure.</p><p>To address these issues, I developed an automation solution using GitLab. The goal was to simplify the certificate update process and make it accessible to all team members, regardless of their technical expertise.</p><h3>Problem Statement</h3><p>The manual renewal of SSL certificates for Siebel on OpenShift was time-consuming and error-prone. Although a detailed user manual was available, it still left room for mistakes, especially for those who were not well-versed in the process. Furthermore, the absence of institutional knowledge meant that delays or errors were likely if the task was left to someone inexperienced. Such mistakes could lead to potential security vulnerabilities or even downtime.</p><h3>Our Solution</h3><p>To overcome these challenges, I implemented an automated solution centered around GitLab. The aim was to create a smooth, error-free process that could be easily executed by any team member, regardless of their background or experience level.</p><h3>Implementation Steps</h3><ol><li><strong>Updating Certificate Files in GitLab:</strong> I wrote a PowerShell script that automates the update of SSL certificate files stored in our GitLab repository. This script ensures that the new certificate is correctly formatted and free of unnecessary spaces or errors before being committed to the repository.</li><li><strong>Deploying Updates via OpenShift:</strong> After the certificate files are updated in GitLab, OpenShift automatically applies the updates to the relevant routes. This integration between GitLab and OpenShift ensures that the new SSL certificate is deployed without the need for manual intervention.</li></ol><h3>Results</h3><p>This automation has significantly transformed the certificate renewal process from a manual, error-prone task to an efficient, streamlined operation. The key benefits include:</p><ul><li><strong>Reduced Errors:</strong> By eliminating manual steps, the risk of human error was substantially reduced.</li><li><strong>Time Savings:</strong> The automation reduced the time required for certificate renewal from several hours to just minutes.</li><li><strong>Increased Accessibility:</strong> Even team members with no prior experience in SSL certificate management can now carry out the renewal process with minimal training.</li></ul><h3>Lessons Learned</h3><p>Throughout this project, I encountered a few challenges, particularly with character encoding and ensuring smooth integration between different tools. However, these issues were successfully resolved, and the experience highlighted the power of automation in DevOps practices.</p><h3>Future Improvements</h3><p>Looking forward, I plan to extend this automation to other repetitive tasks within our Siebel environment. Additionally, exploring AI-driven tools to predict and prevent potential issues before they arise is another avenue worth pursuing.</p><h3>Conclusion</h3><p>Automating the SSL certificate renewal process has not only enhanced our operational efficiency but also strengthened our overall DevOps practices. This project underscores the value of automation and continuous integration in modern software development.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c8e79c20166" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Streamlining the Tedious Package Process for Siebel with Python and Jenkins]]></title>
            <link>https://medium.com/@yener.ipeksac/streamlining-the-tedious-package-process-for-siebel-with-python-and-jenkins-d6f6881f95e8?source=rss-25ac4f22d17d------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6f6881f95e8</guid>
            <category><![CDATA[siebel]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[rest-api]]></category>
            <dc:creator><![CDATA[Yener Ipeksac]]></dc:creator>
            <pubDate>Fri, 22 Dec 2023 10:49:59 GMT</pubDate>
            <atom:updated>2023-12-22T10:49:59.998Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Streamlining the Tedious Package Process for Siebel with Python and Jenkins</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*Lyy5oYwaQ3aEBdnvh6JT6w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/1*0_hs1fkHSMp5SCYhxMxUCQ.png" /></figure><p>‍</p><p>In today’s fast-paced business environment, organizations are constantly seeking ways to optimize their processes and improve efficiency. This is particularly true for companies using Siebel, a powerful customer relationship management (CRM) tool. The package process in Siebel can be time-consuming and prone to errors, but with the right tools and techniques, it can be streamlined to achieve greater efficiency. In this article, we will explore how Python and Jenkins can be used to automate the package process in Siebel, resulting in significant time savings and virtually eliminating manual errors.</p><p><strong>Why Automate the Package Process?</strong></p><p>The package process in Siebel involves several steps, including generating a watermark, transferring it to the source environment, exporting the package, transferring the zip file to the target environment, and finally importing the package. Traditionally, these steps were performed manually, which not only consumed a significant amount of time but also left room for human error. By automating this process, organizations can save time, reduce errors, and ensure a more reliable package process.</p><p><strong>Jenkins Pipeline: Executing Five Essential Steps</strong></p><p>To automate the package process in Siebel, we can leverage the power of Jenkins, an open-source automation server. By creating a Jenkins pipeline, we can execute the five essential steps of the package process seamlessly. Let’s take a closer look at each step:</p><p><strong>1. Generating the Watermark</strong></p><p>The first step in our Jenkins pipeline is to generate the latest package version in the target environment. This is achieved using Python scripts that interact with Siebel’s REST API. The primary objective of this step is to generate a watermark that signifies the current package version. By automating this step, we eliminate the need for manual intervention and ensure the accuracy of the watermark.</p><p><strong>2. Transferring the Watermark to the Source Environment</strong></p><p>Once the watermark is generated, the next step is to transfer it from the target environment to the source environment. Since our Siebel application is hosted within an OpenShift cluster, this task can be easily accomplished using OC CLI commands. The seamless integration between Python, Jenkins, and OpenShift allows for a smooth transfer of the watermark, reducing the risk of errors.</p><p><strong>3. Exporting the Package from the Source Environment</strong></p><p>With the watermark now present in the source environment, we can proceed to export the package using Siebel’s REST API. This step involves creating a package zip file that contains all the necessary files and configurations. To ensure the successful creation of the package, we implement a REST API call every 20 seconds to monitor the status in the migration history. This real-time monitoring helps us identify and resolve any issues promptly.</p><p><strong>4. Transferring the Zip File to the Target Environment</strong></p><p>Once the package is exported, the next step is to transfer the zip file back to the target environment. Similar to the second step, we can leverage the power of OC CLI commands to facilitate this transfer. By automating this step, we eliminate the need for manual file transfers, reducing the risk of data loss or corruption.</p><p><strong>5. Importing the Package to the Target Environment</strong></p><p>The final step in our Jenkins pipeline is to import the transferred zip file into the target environment using Siebel’s REST API. This step ensures that the package is correctly imported and applied to the target environment. As in the third step, we perform a status check every 20 seconds to confirm the success of the package import. This real-time monitoring allows us to detect and resolve any issues promptly, ensuring the integrity of the package.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*elCXRH3LAVTxvr0S0LPsfA.png" /></figure><p><strong>Results: Amplifying Efficiency and Virtually Eliminating Manual Errors</strong></p><p>The integration of automation into the package process in Siebel has yielded significant results. Not only has it expedited our team’s workflow, but it has also led to an extraordinary reduction in manual errors. What once took approximately 15 minutes and was susceptible to human error has now been streamlined to an average of 2 minutes. This dramatic reduction in time not only amplifies efficiency but also guarantees a more dependable package process for our Siebel application.</p><p><strong>Future Endeavors: Integrating Siebel Test Automation</strong></p><p>Looking ahead, we plan to further enhance our automation journey by seamlessly integrating Siebel Test Automation. By combining the automation mentioned in this article with Siebel Test Automation, we aim to create a flawless and rapid automation structure that tests developments across all environments seamlessly and without errors. This transformation is anticipated to reduce the current workflow, which takes days, to mere minutes, all while ensuring a faultless execution. Our ultimate goal is to elevate our automation to this level of efficiency.</p><p>In conclusion, automating the package process in Siebel using Python and Jenkins offers numerous benefits to organizations. By eliminating manual intervention and reducing the risk of errors, organizations can save time, increase efficiency, and ensure a more reliable package process. With the integration of Siebel Test Automation, the automation journey can be taken to the next level, further enhancing efficiency and reducing the time required for testing. Embracing automation is the key to streamlining the tedious package process in Siebel and achieving greater efficiency in CRM operations.</p><p>“Automation is not about replacing people, it’s about making them more productive.” — Arianna Huffington</p><p>Remember, automation is not a one-time effort but an ongoing journey. Continuously evaluating and improving your automation processes will ensure that you stay ahead in today’s competitive business landscape. So, embrace automation, streamline your package process in Siebel, and reap the benefits of increased efficiency and reduced errors.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6f6881f95e8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SIEBEL EXTERNAL TABLE OLUŞTURMA]]></title>
            <link>https://medium.com/@yener.ipeksac/siebel-external-table-olu%C5%9Fturma-e9077cdb1239?source=rss-25ac4f22d17d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9077cdb1239</guid>
            <category><![CDATA[datasource]]></category>
            <category><![CDATA[siebel]]></category>
            <category><![CDATA[external-tables]]></category>
            <category><![CDATA[external-views]]></category>
            <category><![CDATA[definex]]></category>
            <dc:creator><![CDATA[Yener Ipeksac]]></dc:creator>
            <pubDate>Sat, 19 Nov 2022 07:59:02 GMT</pubDate>
            <atom:updated>2022-11-19T07:59:02.690Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><strong>SIEBEL EXTERNAL TABLE OLUŞTURMA</strong></blockquote><p><strong>Selamlar, öncelikle siebel’da external table neden oluşturuyoruz sorusunu yanıtlamak isterim. Siebel’da external table oluşturma sebebimiz, siebel database’inde olan fakat başka bir şemada bulunan tablo ya da başka bir database’de bulunan bir tablodan data çekmek — yetki varsa — ( select ), data yaratmak — yetki varsa — ( insert ), data güncellemek — yetki varsa — ( update ), data silmek — yetki varsa — ( delete ) fonksiyonlarını kullanmaktır.</strong></p><p><strong>Şimdi nasıl yapacağımız konusunda detaylı bilgi vermeye çalışacağım;</strong></p><p><strong>1-</strong> <strong>Hangi tabloda işlem yapacaksak o tablonun viewini oluşturmalıyız.</strong></p><p><strong>Diyelim ki; siebel database’inde siebel şeması dışında bir şemadaki tabloda işlem yapmak istiyoruz bu tabloya bakan db view oluşturmalıyız.</strong></p><p><strong>Örnek; MSFA.BB_ASSET tablosu.</strong></p><p><strong>Aşağıdaki komut ile bu tablonun bir db view’ını oluşturuyoruz. ( bu scriptte tablonun tüm kolonlarını alıyoruz fakat db view oluştururken istediğiniz kolonları da alabilirsiniz ) Ve yetki veriyoruz.</strong></p><p><strong>— — — — — — — — — — — -</strong></p><p><strong>CREATE OR REPLACE VIEW MSFA.TTG_BB_ASSET</strong></p><p><strong>AS</strong></p><p><strong>SELECT *</strong></p><p><strong>FROM MSFA.BB_ASSET;</strong></p><p><strong>GRANT DELETE, INSERT, SELECT, UPDATE</strong></p><p><strong>ON MSFA.TTG_BB_ASSET TO SSE_ROLE;</strong></p><p><strong>COMMIT;</strong></p><p><strong>— — — — — — — — — —</strong></p><p><strong>2-</strong> <strong>Oluşturduğumuz view’in ddl’ini oluşturmalıyız.</strong></p><p><strong>Bunun için birden fazla yol var aslında ben burda birini anlatacağım ( her sql tools’undan ( toad, sql developer vs. ) farklı şeklinde alınıyor. Örnekte SQL Developer üzerinden alınacak.</strong></p><p><strong>Yarattığımız view’in declaration’ına gitmeliyiz. Bunu nasıl yapacağız?</strong></p><p>· <strong>İster view a select çekip, ctrl tuşuna basarak view isminin üstüne tıklayabilirsiniz. Aşağıdaki ekran görüntüsünde tabloya select çekildikten sonra ctrl tuşuna basınca olan görüntü bulunmaktadır.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/758/1*0Iwaiv8qncwETT1OjvJzjg.png" /></figure><p>· <strong>İsterseniz de tabloya select çektikten sonra tablo ismine sağ tıklayıp ‘Open Declaration’ diyebilirsiniz.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*mSQwfQ1D3zJ1YkdnMbPmcA.png" /></figure><p><strong>Her ikisinde de aşağıdaki görüntüdeki sekme gelecektir.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*d8fMoAwABBjLZ787CIX7vg.png" /></figure><p><strong>Burada Actions’a tıklayıp Export diyoruz.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*jU65UuhqcfGU7Y7aJB86kg.png" /></figure><p><strong>Gelen sayfa aşağıdaki gibi olacaktır. Burada datayla işimiz olmadığı için Export Data flagini kaldırıyoruz. Encoding varsa ‘unicode’ seçiyoruz. Dosyayı nereye atacağımızı belirleyip Next diyoruz. Son görüntü aşağıdaki gibidir.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*9FjAp119A1l2XADYHrqSYw.png" /></figure><p><strong>Ardından aşağıdaki görüntüdeki gibi yeni bir bölüm gelecektir, burada herhangi bir şey yapmadan Finish diyoruz.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*aWM_UmeRuTI66pw-QOaSdw.png" /></figure><p><strong>Daha sonra inen dosyamızı kontrol edip doğrulunu teyit ediyoruz. Burada aslında db view i create ederkenki sql in kolonları olan halini göreceksiniz. Eğer 1.adımda db view’i oluştururken select * yerine kolon isimleriyle oluşturduysanız 2.adımı atlayıp direkt o scripti bir sql dosyası olarak herhangi bir yere kaydedebilirsiniz. Bu oluşan dosyaya biz ddl diyoruz.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*kDb5OxvAAORwrkrL6rYb6g.png" /></figure><p><strong>3-</strong> <strong>DDL dosyasını Siebel Tools’a External Table olarak import etmek.</strong></p><p><strong>Siebel Tools’ta Object Explorer’dan Table kısmına gelip aşağıda görüntüde de belirtildiği gibi herhangi bir row’a sağ tıklayıp New Object Wizards.. ardından da External Table Schema Import seçeneğini seçiyoruz.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*iM1-EalI7s_B2UNeNo14GQ.png" /></figure><p><strong>Daha sonra üç alanlı bir ekran açılacaktır.</strong></p><p><strong>İlk alan -&gt; Siebel Project -&gt; lockladığımız siebel projesini seçiyoruz.</strong></p><p><strong>İkinci alan -&gt; Şema kaynağının tipi -&gt; DDL / Analytics</strong></p><p><strong>Üçüncü alan -&gt; İşlemden sonra oluşacak olan external table’in group code’u. -&gt; Yapılacak table ne ile alakalıysa onu hatırlatacak ilk üç harfi girebilirsiniz. Siebel External Table ve External Viewları EX_ prefixyle ve _0000001 suffixiyle yaratıyor, sizin verdiğiniz üç harfi araya koyuyor, eğer aynı isimden iki tane external view ya da external table verirseniz suffix i 1 arttırarak ilerletiyor. Örneğin; üç harf ‘SFA’ vermiş olalım. EX_SFA_0000001</strong></p><p><strong>Next diyoruz.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*2KWlPiStoAsZkuSfVm8YKg.png" /></figure><p><strong>Ardından gelecek olan ekranda bizden external table’in bulunduğu database bilgisini ve 2.adımda oluşturduğumuz ddl’in pathini istiyor.</strong></p><p><strong>Bunları girip next diyoruz.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/478/1*4a8wyvdBy7ugVwKK4-duCQ.png" /></figure><p><strong>Ardından açılacak olan ekranda bize Data Source’u sorup, oluşturulacak olan tablonun ismini gösteriyor. Buradaki örnekte aynı data source daha önceden yaratıldığı için “Runtime Data Source Name” daha önceden ortama tanımlı olan bir data source girilmiştir. Yeni bir data source olacak ise burayı boş bırakarak ilerleyiniz. İlerleyen steplerde burayı nasıl dolduracağınızı anlatacağım. Finish diyoruz.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/631/1*SNvz3AF_31ogZAJzoepIMA.png" /></figure><p><strong>Artık Siebel Tools üzerinde external tablomuz oluşmuş oldu. Burada yazan Alias kısmı external view’in adı olacaktır ( default olarak öyle gelmekte )</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*fKLJEvcaLZ56nNmXHvqaXQ.png" /></figure><p><strong>Bir sonraki adımda anlatacak olduğum Data Source oluşturma adımından önce ( ismini önceden belirlemeniz gerekmektedir ) aşağıdaki kısmı mutlaka doldurmanızı tavsiye ederim. Burada diğer adımda belirtecek olduğumuz DataSource’u ortamda tanımladıktan sonra bu tablonun hangi DataSource üzerinden nereye bağlanacağını sağlamaktasınız. İsterseniz bu tabloya bakan bir Business Component yaratıp ardından Applet yaratıp bu tablo üzerinde hem data gösterip hem güncelleme yapabilirsiniz, isterseniz yaptığınız Business Component’i Integration Object Component’e bağlayıp, Web Servisle başka sistemlere iletebilirsiniz ya da Web Servis üzerinden size gelen bilgileri bu tabloya yazdırabilirsiniz.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*PHPaQWQJLSKKV22lVphokA.png" /></figure><p><strong>4-</strong> <strong>DataSource oluşturma</strong></p><p><strong>GUI de Sitemap üzerinden -&gt; Administration — Server Configuration -&gt; Enterprises — Profile Configuration ekranına gidilir. Burada aşağıdaki gibi Profile Configuration oluşturulur.</strong></p><p><strong>Profile -&gt; Profil ismi -&gt; profile configuration’un ismidir.</strong></p><p><strong>Alias -&gt; Siebel toolsta ve diğer configurationlarda kullanılacak olan Profile Configurationun tanımıdır.</strong></p><p><strong>Subsystem Type -&gt; InfraDatasources olmalıdır.</strong></p><p><strong>Description -&gt; Datasource’in neden eklediği konusunda açıklama yazılabilir.</strong></p><p><strong>Gelelim bu profile configuration’un ( Data Source )’nin parametrelerine (en alttaki applet) , burada önemli olan 8 tane parametre değeri vardır, diğerleri defaulttaki gibi kalabilir.</strong></p><p>· <strong>DSConnectString -&gt; Siebel Server filesystem’inde bulunacak olan ve external table’imizin bağlı olduğu database’in bilgilerinin bulunduğu tnsnames.ora dosyasındaki database’in alias adıdır.</strong></p><p>· <strong>DSDLLName -&gt; sscdo90 olmalıdır.</strong></p><p>· <strong>DSUsername -&gt; external tablonun bulunduğu database’ye giriş yapabilecek kullanıcı adıdır. (tabloya da erişimi olmalıdır.)</strong></p><p>· <strong>DSPassword -&gt; external tablonun bulunduğu database’ye giriş yapabilecek kullanıcının şifresidir. (tabloya da erişimi olmalıdır.)</strong></p><p>· <strong>DSTrxDbConnReconnectIntervalSeconds -&gt; 120 olmalıdır.</strong></p><p>· <strong>DSTableOwner -&gt; External tablonun bulunduğu databasedeki external tablonun yaratıldığı şemanın ismidir.</strong></p><p>· <strong>DSFileSystem ( advanced parametrelerde bulunur) -&gt; Filesystem bilgisidir.</strong></p><p>· <strong>DSSQLStyle ( advanced parametrelerde bulunur) -&gt; OracleCBO olmalıdır.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CfLbCuZ0TDxKYzd7eGl_aA.png" /></figure><p><strong>5-</strong> <strong>External tablonun baktığı DataSource’u kullanabilmek için component datasource’una append etmek.</strong></p><p><strong>4. adımda oluşturmuş olduğumuz DataSource’u nerede kullanmak istiyorsak; örneğin; Bu datasource’u kullanarak siebel gui job tanımlayacaksak Workflow Process Batch Manager componentine, web servislerde kullanacaksak EAI Object Manager componentine, GUI de appletlerde kullanacaksak applicationumuzun bağlı olduğu çalıştığı Application Object Manager componentine aşağıda belirteceğimiz şekilde datasource eklenmelidir.</strong></p><p><strong>GUI de Sitemap üzerinden -&gt; Administration — Server Configuration -&gt; Enterprises — Component Definitions ekranına gidilir. Burada ilgili component query edilir ve Menu’den Start Reconfiguration seçilir.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*o3BeHsuFVALv2URpH7lsug.png" /></figure><p><strong>Ardından en alttaki applette “OM — Named Data Source name” parametresi sorgulanır ( tırnaklar olmadan ). Ve value değerine yeni oluşturduğumuz DataSource’un Alias ismi varolan değerin sonuna , koyarak yazılır. Kayıt kaydedilir (CTRL + S ).</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*KkTLzNNiEtFLFVrmRutdkg.png" /></figure><p><strong>Daha sonra bir üstteki applette ( Component Definitions ) Menu ye tıklanarak, Commit Reconfiguration denir.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*_jEQmm2-hslUySYGBzgnZw.png" /></figure><p><strong>Ardından ilgili componentlere ya da siebel enterprise’a komple restart atılır ve data source kullanılabilir durumda olacaktır.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9077cdb1239" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Siebel Toolsta Olmayan Workflow’u Veritabanından Çekme]]></title>
            <link>https://medium.com/@yener.ipeksac/siebel-toolsta-olmayan-workflowu-veritaban%C4%B1ndan-%C3%A7ekme-c079a26f0c94?source=rss-25ac4f22d17d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c079a26f0c94</guid>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[xml]]></category>
            <category><![CDATA[siebel]]></category>
            <category><![CDATA[definex]]></category>
            <category><![CDATA[base64]]></category>
            <dc:creator><![CDATA[Yener Ipeksac]]></dc:creator>
            <pubDate>Wed, 08 Dec 2021 12:33:55 GMT</pubDate>
            <atom:updated>2021-12-08T12:33:55.690Z</atom:updated>
            <content:encoded><![CDATA[<p>Selamlar,</p><p>Siebel’da yaşanan en büyük problem nedir diye sorsanız Siebel Tools alignment eksikliği derim herhalde. Bazen local toolslardan yapılan geliştirmeler server tools’a align edilmeyip production ortamına kadar gidebiliyor. Haliyle bu geliştirmeyi yapan arkadaşlar işten ayrılmış olabiliyor. Dolayısıyla bu geliştirmelerde bir sorun olduğunda ya da üstüne geliştirme yapılacak olduğunda bu durum fazlasıyla can sıkıcı hale geliyor. En azından Siebel Workflow için bunun çözümü bulunuyor. Production veritabanından direkt olarak ortamda bulunan workflowun xml’ini çekebiliyoruz. Bunun nasıl yapılacağını adım adım anlatmaya çalıştım.</p><p><strong>1.Databaseden sorgu ile workflowun değerlerini Base64 formatlı çekmek.</strong></p><p>Aşağıdaki sorgu sayesinde gui ye import edilen workflowun base64 formatındaki datayı çekiyoruz. Burda önemli nokta sorgudan ne kadar kayıt gelirse gelsin aşağıdaki ekran görüntüsündeki gibi CTRL + A yapıp hepsini seçip kopyalayıp, notepad++ gibi bir uygulamaya yapıştırmamız.</p><p>select d.data_val from siebel.s_wfa_data d inner join siebel.s_wfa_dploy_def w on w.row_id=deploy_def_id where w.name =’WORKFLOW ISMI’ and DEPLOY_STATUS_CD=’ACTIVE’ order by D.SEQ_NUM;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vY8UT3JOTlcfV1QhAGTnvQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SFNuxsPr_elrQx8GMQi_Zw.jpeg" /></figure><p><strong>2.Notepad++ ‘a yapıştırdıktan sonra | işaretlerini silmek.</strong></p><p>Aşağıdaki ekran görüntüsündeki gibi notepad++ taki replace özelliğini kullanarak yazımızdaki | işaretlerini siliyoruz. Küçük pencerenin açılması için ctrl + f yapmamız gerekmektedir. Ordan Replace tabına tıklamamız gerekmektedir.</p><p>Find what: |</p><p>Replace with: boş seçip Replace All yapıyoruz.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9b2SopmpeIjaw2Am3s8UwQ.jpeg" /></figure><p><strong>3.Yazının son halini base64 to ASCII yapmak</strong></p><p><a href="https://base64.guru/converter/decode/ascii">https://base64.guru/converter/decode/ascii</a> linkini kullanarak ( ya da farklı bir site tercih sizin ) aşağıdaki ekran görüntüsündeki notepad teki yazının son halini komple kopyalayıp Base64 alanına yapıştırıp “Decode Base64 to ASCII” butonuna basıp aşağıdaki değeri kopyalamalısınız. Çıkan değer sizde göreceksiniz ki xml hiyerarşisi şeklindedir. Bu yazıyı notepad++ a yapıştırıp xml olarak çıktı alabilirsiniz.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8AiRDY9QrtJxEiL53n1N4Q.jpeg" /></figure><p><strong>4.Çıkan XML formatlı dosyayı , toolsa import etmek.</strong></p><p>Siebel toolsa girip Object Explorer -&gt; Workflow Process tabına gidilir ve herhangi bir workflow’a sağ tıklayıp, ekran görüntüsünde yeşil ile işaretlenmiş alanda bulunan yazıya tıklayarak workflow’unuzu xml şeklinde import edebilirsiniz.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UT0JWTR3g0euEz824ccHTw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c079a26f0c94" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>