Q: I cannot see Strategy Designer in the main menu. Why?
A: You may not have the necessary user role assigned. You need to have at least the View Strategy Designer role.
Q: Can I use Strategy Designer to modify other logics, such as Quotes or Rebates?
A: No, Strategy Designer works only in tandem with the Price Setting Package accelerator. No other use cases are supported at the moment. There is, however, Formula Designer in the Agreements Accelerator that enables visual configuration of Formula Types.
Q: I cannot activate a new draft data lookup or snippet that I created. Is it a bug?
A: This is on purpose. You can activate new draft lookups and snippets by using them in a strategy and activating the strategy.
Q: I cannot change a name of my Strategy / Snippet / Lookup. Why?
A: You can only edit the name of your Strategy, Snipper, or Lookup before you activate it for the first time. After the first activation, the name of the entity must remain consistent for the PSP to use it.
Q: I have set up a range data lookup and want to change it. But the ‘Enable range lookup’ is disabled. Why?
A: If the lookup is already used in a strategy, you cannot change the range definition. You either need to delete the corresponding lookup block from your strategy, or create a new one by duplicating this one and saving it as a new data lookup.
Q: Where can I report bugs and suggest ideas?
A: Use the PFUN project in JIRA. When submitting a ticket, be sure to set the Component to Strategy Designer.
Q: Strategy Designer Data Lookup returns null. What is the fix?
A: Strategies must be redeployed for the fix to take effect.
Q: One of my blocks now shows as “(broken block)” and my strategy is marked Invalid. What happened and can I recover?
A: Because almost everything in Pricefx is dynamic, a change to something a block depends on (for example, metadata that a block relied on is no longer available) can mean that Strategy Designer cannot recreate that block exactly as it was saved. Instead of failing the entire workspace with a broken workspace error, Strategy Designer now renders a placeholder block-labelled (broken block), that is reconstructed from the block data stored in the database. This lets you still open the workspace, see all the other blocks that work correctly, and recover from the missing ones.
To recover, replace the placeholder (broken block) with a working block and reconnect its inputs (for example, the SKU input and the connected ProductID (String) value), then save the strategy again.
Note that while a placeholder (broken block) is present, the strategy is marked Invalid and cannot generate code, so it cannot be deployed until you replace the placeholder. Not every dependency change produces a placeholder block. For example, removing a Price Parameter that a Data Lookup depends on shows a missing-Price-Parameter error in both the Data Lookup and the strategy that uses it rather than a placeholder block.