Skip to main content

This is more directed specifically at Planview but good awareness for other customers as well. 

When utilizing SOAPUI calls there are some characters that cannot be passed. 

It is our understanding that per Planview's security rules that PVMaster password can no longer be something the customer identifies but instead an autogenerated password that Planview creates and then advises the customer on what that password is. 

When using this new password within SOAPUI calls it has to be wrapped in CDATA tag because of the characters needing to be passed.  Why would an autogenerated password be created that violates character rules?  Ideally this would exclude some characters so this additional step is not needed.

I thought about adding this as an enhancement request but my assumption is that the number of participants within that campaign that understand this technical component would never allow it to reach the required number of votes to be reviewed further.  If that assumption is wrong and that is the better path for something like this then please do let me know.

 

Thank you

Pam Sargent

@pamela.sargent  Thanks for bringing this up! If the autogenerated password includes characters that require additional handling in SOAPUI calls, it makes sense to consider excluding them to streamline the process.

I’d recommend submitting this as an enhancement request so it can be properly reviewed by the product team. Even if the campaign doesn’t gain immediate traction, it ensures visibility and allows other users facing similar challenges to contribute their input.


Reply