Why I do not use PowerConnect to access PeopleSoft Tree
Posted by Dylan Wan on March 16, 2011
1. It does not allow you to use parameters to the PeopleSoft connect. It may be changed later. However, it was a big issue when we try to address customer issues.
2. It requires EFFDT as an input.
It expects that people change the EFFDT using Mapping Editor. How can a business user does that every month?
3. It asks for a Tree Name. Many PeopleSoft tree structure supports multiple trees. Tree is just a header of the hierarchy. Whenever you add a new Tree, you need to create a new mapping!!
It does not make sense to use PowerConnect due to the customer demands. All above requirements are from customers.
We have no choice but stop using it.
It is a nice feature, but it was not designed for a prepackaged apps.