Posts of Avantika RSSSun, 24 Nov 2024 23:03:33 GMTIn the previous post, you learned how run time is calculated and the factors influencing report performance. In this post, we will explore each of these factors in detail and understand the best practices to follow for optimizing report performance.Data SourcesStandard Data Sources: These are more flexible but can take more time to process compared to Indexed Data Sources. Using Standard Data Sources can be beneficial for real-time data, effective-dated data, and future-dated data. Since not all business objects in Workday have an Indexed Data Source, sometimes this will be your only option. Select the data source that is closest to your requirement. Using a Standard Data Source with built-in filter and prompts can be faster compared to using a data source without any data source filter/prompts.Indexed Data Sources: These are optimized for performance and provide faster data retrieval. Use Indexed Data Sources whenever possible to enhance report performance.Best Practice: Prefer using Indexed Data Sources for better performance. If you must use Standard Data Sources, ensure they are necessary and consider other areas to improve performance. Filters and PromptsBuilt-in Data Source Filter and Prompts: Data source filter and prompts are more optimized to filter data in report. Try considering this first to filter data before adding your own filters. Efficient Filtering: To reduce processing time, apply filters that narrow down large data sets to smaller. Example: If the requirement is to get all employees from Germany and the Hire Date falls into the period then in this case 1st filter should be countries in the selection list Germany and then add hire date criteria in the filter. By this approach you will first country filter will remove most of employees from data selection and the second filter will apply only on employees from Germany so it will be much faster compare to having it vice versa.Avoid Complex Filters: Avoid using calculated fields in filters and minimi... Read more

]]>Sun, 24 Nov 2024 23:03:33 GMTIn our previous posts, we discussed the importance of optimizing Workday report performance and the downsides of poorly optimized reports. Now, let's dive into how report run time is calculated and factors influencing run time .What is Report Run Time?Report run time refers to the total duration it takes for a report to complete its execution from the moment it is initiated until the final output is generated for rendering on a page or as a file. How Run Time is CalculatedThe calculation of report run time can be broken down into three main stages:Time in QueueDescription: When a report is initiated, it enters a queue to wait for available system resources.Factors Influencing Run Time:The current system load.The availability of resources.High demand on system resources, which can increase this waiting time.Data Retrieval and ProcessingDescription: Once the report begins execution, it retrieves and processes the necessary data based on the report's logic.Factors Influencing Run Time:Data Source Used: A Standard Data Source takes more time compared to an Indexed Data Source. Even for a Standard Data Source, if a particular data source with less instance is not used, it may cause additional delays.Filters and Prompts: Efficient use of filters and prompts can reduce the data volume and improve run time. However, poorly designed filters can increase processing time.Fields: Calculated fields add extra processing steps to the report. The more calculated fields a report has, the longer it may take to run.Security: User security is evaluated for each field to ensure that the user has the appropriate access permissions. This evaluation process can take time, as it involves verifying access for multiple fields to maintain data security and compliance.Sorting: Sorting large data sets can take additional time, especially if multiple columns are being sorted or if the data is not indexed. This step adds to the overall processing time, as the system needs to organize the data in t... Read more

]]>Sun, 24 Nov 2024 15:11:51 GMTIn our previous post, we discussed the importance of report performance in Workday and how it can significantly impact business operations. Now, let's explore the other side of the coin - the consequences of poorly optimized reports.The Negative Impacts of Slow or Inefficient ReportsUser Frustration and Decreased Productivity Slow reports are a source of frustration for users. When employees have to wait for reports to generate, it disrupts their workflow, leading to decreased productivity and morale. Over time, this frustration can accumulate, affecting overall job satisfaction and efficiency.Delayed Decision-Making Poorly optimized reports can take an excessive amount of time to run. When critical business decisions rely on these reports, delays can lead to missed opportunities, slower response times, and an inability to act on insights promptly. In fast-paced industries, even minor delays can have significant impact on business.Increased Operational Costs Inefficient reports can significantly increase tenant resource usage, leading to slower page load times in Workday and causing multiple processes to run longer than necessary. If report performance is not optimized, organizations may need to request Workday to enhance tenant performance by allocating more resources. This ultimately means higher costs for companies, as they have to pay for the additional resources to maintain acceptable performance levels. Time-Out Issue Poorly optimized reports can lead to significant timeout issues. A report embedded in a worklet may take too long to load and eventually time out. Users may be forced to rerun the report, wasting valuable time and encountering the same issue repeatedly, which erodes confidence in the reporting system and hampers productivity.Expectation of Report Performance Based on User Categories Different user groups within an organization have varying expectations for report performance based on their specific needs and roles. Below is an outline from slowes... Read more

]]>Sun, 24 Nov 2024 13:16:13 GMTWelcome to our Workday Report Performance series! In today's fast-paced business environment, accessing reliable and efficient data is critical to making informed decisions. This series is dedicated to helping you understand the why Workday report performance is important, how run time is calculated, different component in report that can affect performance and best practice to develop performance optimized reports. Why Report Performance is ImportantOptimizing report performance in Workday is crucial for several reasons:Speed and Efficiency: Faster reports mean quicker access to insights, enabling timely decision-making.User Satisfaction: Optimized reports enhance user experience, reducing frustration and increasing productivity.Adoption Rate: Optimized reports will increase adoption rate of report/Workday in organization.  Tenant Performance: Optimized reports help minimize system downtime and resource usage, ultimately not slowing other process.What We Will Cover in This SeriesIn this series, we will dive into the following topics:The Downside of Poorly Optimized Reports: Explore the negative impacts of slow or inefficient reports, including delayed decision-making and user frustration.Understanding Report Run Time Calculation: Learn how report run time is calculated and the key metrics involved in measuring performance.Components Affecting Report Performance: Identify the various components that influence report performance.High-Level Process to Create Workday Custom Report and Best Practice: Get insights into best practices for developing performance-optimized reports.Advanced Optimization Techniques: Dive into advanced tips and techniques for further improving report performance.In the Next PostIn the next blog post, we'll dive into the The Downside of Poorly Optimized ReportsSpread the KnowledgeIf you found this post helpful, don’t keep it to yourself! Share it with your colleagues, networks, or on social media ( ProspectSpace , LinkedIn or X) to help others... Read more

]]>Sat, 23 Nov 2024 22:39:18 GMTIn the fast-paced world of Human Capital Management (HCM), having efficient workflows is crucial for organization. Workday, a leading HCM system, provides powerful tools to streamline these workflows through its Business Process framework. But what exactly is a business process in Workday, and why is it so important?In this blog post, we’ll dive into the concept of Workday Business Processes, explaining how they automate and simplify HR, payroll, and financial tasks.We will also highlight the key business processes within Workday HCM, such as hiring, terminations, and performance reviews, and show how they contribute to the smooth and efficient operation of an organization.Whether you're new to Workday or looking to optimize your existing setup, this guide will give you valuable insights into making the most out of Workday's capabilities.Let’s get started!What is a Workday Business Process?In simple terms, a business process in Workday is a series of steps that automate HR, payroll, and benefits tasks. These steps ensure everything is done consistently, accurately, and according to company policies. You can customize these processes to fit your organization’s needs.A typical Workday Business Process includes:Steps: Tasks that need to be completed.Conditions: Rules that determine if a step should be carried out based on certain criteria.Approvals: Points where approvals are needed from managers or other stakeholders.Notifications: Alerts sent to relevant parties at different stages of the process.Security Policy: Who can initiate which action of that particular Business Process.Using these processes, you can automate repetitive tasks, reduce manual errors, and ensure every step is completed correctly.Key Business Processes in Workday HCMWorkday offers several key business processes that are crucial for effective Human Capital Management. Here are some of the most important ones:Create Job RequisitionThis business process is formally requesting to fill an open job pos... Read more

]]>Sun, 03 Nov 2024 18:38:41 GMTIn today’s dynamic business environment, effective Human Capital Management (HCM) is essential for operational success. Workday, a leading HCM system, offers robust organizational structures that enable companies to manage their employees and operations efficiently. Understanding these structures is crucial, as they play a pivotal role in defining reporting hierarchies, budgeting, payroll administration.. etc.In this post, we will dive into the various types of organizations within Workday, including companies, cost centers, and supervisory organizations. We will explore purpose of organization and usage. Here are the different types of Workday organizations, each serving distinct purposesSupervisory Organizations Purpose: Serve as the primary building blocks for modeling the reporting structure within a company. They define management and reporting relationships. Usage: Used to manage employee assignments, staffing models, and hierarchies. Company Organizations Purpose: Represent legal business entities for financial processing. They are essential for managing financial data. Usage: Used in financial and payroll reporting to segregate data by legal entity. Cost Centers Purpose: Used for tracking and controlling expenses. Cost centers are critical for budgeting and financial analysis. Usage: Assign employees to cost centers to manage and report on where costs are incurred within an organization. Business Units Purpose: Represent functional areas within an organization that are responsible for specific business operations. Usage: Often used in financial reporting to segment operational data and in managing operational tasks across different areas. Regions Purpose: Used to represent geographical locations or areas within Workday. Helpful for managing location-specific data and compliance. Usage: Can be used for reporting and tailoring business processes to specific regional requirements. Custom Organizations Purpose: Allow organizations to define additional organizati... Read more

]]>Sun, 03 Nov 2024 16:35:54 GMTAs a report developer, we should always use best practices to create a report and ensure that users can run reports quickly to get the desired results. In this post, I will cover High-level processes to create your custom report, best practices, and how you can optimize your report for performance.High-Level Process to Create Workday Custom Report:Determine Report Type: For summary view use matrix and composite report. For data in tabular format, your first preference should be the advance report type.Select Data Source: Determine which data source to use based on the field list. Your goal should be to pick a data source that returns fewer results but includes the majority of the fields required for the report. If a field does not exit on the primary business object, ensure that you have a linkage to a related business object to achieve the desired outcome.Create Custom report: Below steps outlined based on report type custom report but it may very based on report type.Access Task “Create Custom report”Type Custom Report Name (Keep is short and ensure that outlines the purpose of report)Select Data SourceSelect the field requested in in column section of report. If some fields does not exists then create a calculated field based on existing fields.Apply sorting if neededApply filter to get desired population in reportApply sub filter if data needs to be filter for related business objectPopulate Prompt if any and level them with user friendly names.Share the Report with require recipient so that they can find report and run in workday.Best practice to consider while developing Workday custom reportUtilize the optimized version of the standard data source, for instance, Indexed data source: Indexed Workers or Worker for HCM Reporting. Additionally, using a standard data source with a defined prompt can be faster compared to using a data source without any prompts.Organize your filter criteria- Apply filter from discard population from most to least. Example: If the r... Read more

]]>Sun, 03 Nov 2024 15:39:19 GMTWhat is Integration?Think of integration as building a bridge between two towns so that people and resources can flow smoothly. Picture this: you reside in Town A with an amazing bakery, but work in Town B with a fantastic coffee spot. The catch? There’s a river in between without a bridge. Well, integration steps in as the hero, constructing that bridge to link the two towns. This way, you can easily grab fresh bread from Town A and pair it with your go-to coffee from Town B. In the tech realm, imagine Town A and Town B as different software applications or systems, and the river as the barrier preventing seamless information sharing or collaboration.Just replicate same example from Workday perspective: Integration between Workday (Town A) and Active Directory (B) . Workday (Town A) have employees data and Active Directory (B) has email data. Both system needs information from each system to function properly or enhance user experience with that data. In this case integration between these two system will work as bridge to share data.Type Of IntegrationIntegrations with Workday can generally be classified into two main patterns: Inbound and Outbound.Inbound Integration: This involves sending data into Workday from external systems. For example, importing employee data from a recruiting platform(Taleo) into Workday.Outbound Integration: This involves sending data from Workday to other systems. For example, exporting payroll data from Workday to a banking system for processing payments or sending Workday employee data to an external benefits provider.Workday Integration ToolsWorkday provides different tools to build integration(bridge) with other systems. These tools can be used to build varieties of integration ranging from simple to complex, real-time data exchanges. The main tools include:Enterprise Interface Builder (EIB) is a user-friendly tool that makes it easy to create integrations for importing data into Workday or Exporting data from Workday. EIB has a gui... Read more

]]>Sun, 03 Nov 2024 15:30:12 GMTWhen leading a Workday Integration design session, the goal is to gather as much detailed information as possible to ensure the developed solution meets all functional, technical, and business requirements.Below are sample questions to start with in your first design calls.General and Scope QuestionsWhat are the source and target systems of this integration?What is the purpose of the integration? (To understand the high-level goal and the problem it aims to solve.)Who are the stakeholders and end-users of this integration? (To identify all parties involved or affected by the integration.)What is the current process and how is data fed into the system? (To understand the current process and so that you can understand how to transform it into Workday.)What are the key business processes this integration will support? (Understanding the processes helps in tailoring the integration to business needs.)Which Workday modules (HCM, Financials, Payroll, etc.) does this integration involve?What type of data will be transferred? (Employee data, financial records, etc.)How frequently does the data need to be updated? (Real-time, batch processing, etc.)Are there specific data validation rules that need to be applied?Technical RequirementsDo you have any specification guide to provide requirements?If the above is no, could you please provide us list of fields needed in the interface? (it should contain – Field Name, Description, Type, require or Optional, format, Transformation rule, constant/default value) – Note: As a developer, you should work offline to map vendor fields with Workday and in the second design session you should discuss any open items on field mapping.Do you have any preferences or requirements for the integration pattern? (REST/SOAP APIs, file-based, etc.)What are the data formats required for the integration? (XML, JSON, CSV, etc.)Are there specific security or compliance requirements? (Encryption, Key Base Authentication, Data Privacy Approval..etc.)How will... Read more

]]>Sun, 03 Nov 2024 15:19:42 GMTCustom report in Workday is essential for transforming raw data into valuable insights to take informed business decisions. As a report developer, we should ask the below questions during the design session. This will help us to select and determine the report type and requirements for the report.What is the primary purpose of the report? Understanding the main objective of the report helps us determine its scope, content, and format, ensuring it meets the stakeholders’ needs.Who are the primary users of this report?Knowing the audience allows us to tailor the report’s solution. example: If this report is for management then probably they will need high-level data and going into details. if that report is for some audit then the business will need data at a much more detailed level.What specific data fields do you need in the report?This question helps identify the exact data that needs to be included, ensuring all necessary information is captured for analysis or decision-making.What should be filter criteria for report?This will help us to ensure that only required population is appearing in report.Do you need any prompt on report to extract data based on that?Goal of this question to get the prompt value that needs to added in report to fetch data based on prompt.How data should be displayed in the report (summarized view or detailed view)? Do you require any interactive features, such as drill-down capabilities or filters?Interactive features can enhance the usability of the report, allowing users to explore the data more deeply based on their specific questions. This question will also help us to determine type of report that needs to be created.Are there any similar reports currently being used that this new report could replicate or improve upon?Reviewing existing reports can provide a starting point and help avoid duplication of efforts, while also identifying opportunities for improvement. If project is an implementation project then we can ask if any simil... Read more

]]>Thu, 24 Oct 2024 21:02:54 GMT