Hold up, are we talking about Pega activities or doing laundry? Cause keeping it short and sweet is always a good idea, no matter what you're doing. But 15 steps, that's rookie numbers! Let's aim for 5 or less, folks.
A, C, and E are the obvious choices here. Who wants to write a million steps in one activity anyway? As for the activity call limit, that's just a recipe for a headache if you ask me.
I'm going with A, C, and E. Keeping activities short and using alternative rule types are definitely best practices. As for the activity call limit, I'm not convinced that's necessary in all cases.
A, C, and E for sure. Limiting custom Java is always a good idea, and using alternatives to activities can help with performance. Not sure about the activity call limit though, that seems a bit arbitrary.
Hmm, this is a tricky one. I think A, C, and E are the best practices, but I'm not sure about the limit on activity calls. Guess I'll have to review my Pega best practices guide again.
Dorothy
2 months agoRebecka
26 days agoEzekiel
1 months agoGiuseppe
1 months agoShanda
2 months agoHelaine
1 months agoLettie
1 months agoCassandra
2 months agoArgelia
3 months agoChi
2 months agoShawnna
2 months agoTamera
3 months agoEzekiel
3 months agoHeike
1 months agoRyan
2 months agoKandis
2 months agoStephaine
2 months agoGladys
3 months agoReyes
3 months agoEdison
3 months ago