![]() Because BPF’s integrate alongside security roles, it is possible to dictate which process applies for a subset of users within the application.In the example shown earlier, the BPF is designed to “crossover” from the Lead to the Opportunity table as you progress through each stage. BPF’s can span multiple tables if required.Some other valuable features regarding BPF’s are worth highlighting at this stage: Note that they do not move the process to the next step but will enable you to preview the details needed as part of the next/previous stage. The arrows at either end of the BPF allow you to toggle the current, focused stage.Abandoned BPF’s will be marked clearly within the application, as indicated in the screenshot below: You can choose to switch to another available process or even abandon the current BPF entirely. Users have several options underneath the Process dropdown field on the ribbon.We can also see the amount of time the BPF has resided in this particular stage. The stage which is coloured is the current, active stage in the process, which, in this case, would be the Qualify stage.Users can expand any active/inactive stage to review the details required. In this case, having expanded the Qualify stage, the user is prompted to provide additional information, such as Estimated Budget and details of any existing Contact or Account row. A BPF is structured by stages, which the user can click on to view the further details required to proceed to the next step.Here, the user can view details about the name of the BPF and also how long the current process has been active in this case, for around five months.Users have access to the following features when using a BPF, indicated by the numbers above: The screenshot below illustrates a BPF called the Lead to Opportunity Sales Process, which is associated with the Lead table: As part of this, we can tailor many aspects of either an existing or new BPF and integrate the tool alongside other features within the Power Platform. You can then apply this at the table level within a model-driven Power App. Without the ability to comfortably accommodate these scenarios, it becomes incredibly challenging to meet the business and end customers’ expectations.īusiness Process Flow’s (or BPF’s) aim to address these concerns by allowing developers to model out and enforce a business process effectively. Consider another scenario involving a case management process a service desk manager needs to ensure that a case proceeds according to any agreed SLA’s with an end customer and, where appropriate, they must monitor how long a Case has resided within a specific stage. Achieving this objective ensures you can guide end-users towards the correct outcome for, let’s say, a sales process and guarantee the population of accurate data to progress to the next stage. As such, following an approved business process within them becomes necessary. In our discussion around model-driven Power Apps, we highlighted that these are, in effect, data-driven applications. ![]() Ideally, your revision should involve a high degree of hands-on testing and familiarity working with the platform if you want to do well in this exam. Let’s dive in and see what they are all about!Īs with all posts in this series, the aim is to provide a broad outline of the core areas to keep in mind when tackling the exam, linked to appropriate resources for more focused study. They also have powerful features that can address common automation scenarios for actions performed at the server level. The tools referenced above - Business Process Flows and Business Rules - are perhaps most advantageous from a client-side perspective. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |