Welcome to Open Discussion

Erik H — Wed, 27 Mar 2019 03:39:56 -0000

I've released v0.70, which should be able to handle some recently introduced PeopleCode bytecode. I can't test it myself, so please let me know if you run into trouble.

Welcome to Open Discussion

Erik H — Tue, 12 Feb 2019 12:03:25 -0000

The problem is not so much getting the information out of the PeopleTools tables, but getting it back in... For a record definition, for example, you'd have a bunch of values representing things like field names, types and edit details. When you want to restore a record definition, you not only have to put that information back into the correct peopletools tables, but you also have to create or modify the corresponding database table.

I believe the commercial Application Change Management tools (Stat, Phire Architect, CAPI) heavily depend on calling App Designer in batch mode for this. This approach probably makes sense - rather than figuring out all the details of the ptools tables, focus on exporting and importing projects.

Welcome to Open Discussion

Minh — Tue, 12 Feb 2019 09:29:57 -0000

Hi Erik,

Thank you for your response. I was hoping that maybe there is a way to do it but like you said that will be too complicated or impossible.

Alphonse also said that he, and probably you, know how to extract from database other object like tables, menus... I'm sorry for bothering you but can you please explain it to me how can i improve the code to do it? Any details would be really helpful :)

Minh

Welcome to Open Discussion

Erik H — Tue, 12 Feb 2019 03:04:56 -0000

Hi Minh,

No, there is no automated way to import the extracted files. Implementing that would involve not only compiling the plain text PeopleCode back to bytecode (which should be possible), but also writing that bytecode to the PeopleTools tables; that may be taking things too far. Or, you'd have to find a way to make the App Designer do it, but I don't know how (expect by just importing projects).

Basically, this tool does version tracking, it's not really version control. Its best feature, in my opinion, is that you can have it run every night or so, making it store all modified PeopleCode and SQL in git or SVN.

Hope this helps,

Erik

Welcome to Open Discussion

Minh — Mon, 11 Feb 2019 13:07:42 -0000

Hi Alphonse,

Can you tell me if there is a way to import all extracted files to PeopleSoft?

Thanks
Minh

Welcome to Open Discussion

Hadrien Thivellier — Thu, 31 Jan 2019 14:54:40 -0000

Hi Alphonse,

It is more clear to me.
I'll provide those information to my team and I (or they) will comeback to this discussion if any additional information is necessary.

Thank you for your quick answers.

Regards,
Hadrien

Welcome to Open Discussion

Alphonse — Thu, 31 Jan 2019 14:46:26 -0000

Hi Hadrien

no is also applicable to tables, screens, menus...

Currently PcodeDecode extract current things :
- Peoplecode of any objects
- SQL of any objects (including SQL of Views And Application Engine)

Nothing else.
Adding a technology is not the bigest things to do.
Generating a file from An element in the PeopleSoft Table are not so complicated ...

For your Git use, if you want to use the Git fonctionality of DecodePcode
Pcode Decode create a commit for each object modified in the database.
Currently it didn't start from a procjet definition and create a single commit for each project ...
It will create a commit for each PeopleCode ...
We (I) have to rewrite the code to take this approach.
It's in my to do list, but not a priority for my current client ...
Currently I am alone to maintain this project ...
So I can't give you any visibility ...

Regards

Alphonse

Welcome to Open Discussion

Hadrien Thivellier — Thu, 31 Jan 2019 14:08:04 -0000

Hi Alphonse,

Thank you for your answer.
Sorry, but I'm not familiar with PeopleSoft vocabulary. I try to repeate what development team try to explain to me. Like you mention if SQR is not stored in database, I don't have the needs for SQR.

However, when you say "no", is it only for SQR or it is also applicable to tables, screens, menus...?

Basically, develoment team explains : because PeopleSoft is database based application, it is not possible to have the full scope of the application translate in text (SQL) based, only the pure SQL and PeopleCode can be text based. All other object can't.

Because development team are not only working on PeopleCode, I want to know if DecodePcode manage the PeopleSoft standard item as well so I can plug GIT for the full scope of the development work.

Regards,
Hadrien

Welcome to Open Discussion

Alphonse — Thu, 31 Jan 2019 11:27:34 -0000

Hi Hadrien

At this moment No. (but I know how to update the code do it ... But It's very hard to find the time to make an evolution on this program ... )

SQR I can't why you want to use DecodePcode because SQR are not stored in the database.
You can ever see the SQR file on your server so DecodePcode should be useless for SQR.

Regards

Alphonse

Welcome to Open Discussion

Hadrien Thivellier — Thu, 31 Jan 2019 09:53:20 -0000

Hello, I'm project manager for DXC Technology.
I'm working on a DevOps transformation intiative for multiple clients.

Today one of our delivery team is working on PeopleSoft with standard tools like Application Designer to develop and STAT to deliver. My understanding is that developement team also use STAT like configuration manger tool but I'm not sure thist is the best tool in DevOps chain.

I would like to use PeopleCodeDecode which looks to answer my need. Development team raise a potential issue in the use of PeopleCodeDecode because they think it will only export PeopleCode.

Question is: is PeopleCodeDecode extract from database all PeopleCode object like fileds, tables, screen, menus, application engine, SQR, parameters and not only PeopleCode and SQL?

Best Regards,
Hadrien Thivellier

Recent posts to Open Discussion

Welcome to Open Discussion

Welcome to Open Discussion

Welcome to Open Discussion

Welcome to Open Discussion

Welcome to Open Discussion

Welcome to Open Discussion

Welcome to Open Discussion

Welcome to Open Discussion

Welcome to Open Discussion

Welcome to Open Discussion