Character Limit for New Rest Integration and Class Name

General
, , , , , ,
1

Dear Pega,

Please increase the character limit for the class name for new REST integration and the character limit for the class name.

Using the refactor functionality to rename the classes and manually having to run the refactor for each individual child class takes a considerable amount of time.

What normally takes about 10 minutes, turns into a couple our venture and make me want avoid using the the new REST integration function.

2

@ASHLEYM82

You have to raise a ticket with Pega in you MSP portal https://msp.pega.com. Pega GCS will connect with you with your requirements. If they feel that a patch is required, they’ll raise a feedback request and provide you with a FDBK ticket ID. That ticket is tracked in Pega’s internal agile studio which is not accessible to clients. They pickup these requests based on importance and if its approved by the product team, its implemented and released in the upcoming releases. Your Pega Account Executive should be able to help you with the process. You can get more info on how they’re tracked here:

https://support.pega.com/support-doc/what-expect-after-support-ticket-resolution

3

Hi @ASHLEYM82

Change the precondition of step 1 in activity pyGenerationCheck of class
Pega-DataModel-DataSources-REST based on your requirements in case you want to increase the length of the class.

Hope it helps.

Thanks

Megha

4

@ASHLEYM82 FDBK-65555 (Restricting the Class name size while creating a new application) already exists for consideration for future products.

Please can you click Accept solution against the reply which unblocked you?

5

@SohamM95 Thanks, I initially found the wizard helpful, but after using it a few times the clean up task was way to cumbersome. It was much easier and quicker to build by scratch. Hopefully Pega continues to expand on their wizards and allow a little more granular control.

6

@xJubeix Best Option I found to work so far is that you create using the wizard. Then rename the class using Class refactor.

7

@Megha007 I am hesitant to make modifications likes, in the past things would come back to haunt us if we opened a SR with Pega. =\

8

@xJubeix I agree. It depends on the data mapping or how big the Rest service is. Class refactor is a big time consuming task if there are so many rules in the application/DataBase.

9

@MarijeSchillern Thanks for the reply. The issues wasn’t with a new application; it was an existing application. I’ve decided against using the wizard due to the clean up involved and found it a lot easier and less time consuming to manually build the response and requests.

10

@VenkatRaman That is what I was doing, but the Wizard was creating names that were too long for some classes. So I had to manually create the classes and delete the classes that were not refactored. I ended up spending more time correcting the wizard mess than it takes manually creating everything.