- Posts: 604
- Thank you received: 82
AETLP Suggestions
- bruce.gibbins
- Topic Author
- Offline
- Platinum Member
-
3 years 10 months ago - 3 years 10 months ago #19673
by bruce.gibbins
AETLP Suggestions was created by bruce.gibbins
Hi.
I believe is great value for money and very feature rich. With that in mind there are a couple of things that I come across when using it that I believe would be worthwhile enhancements
1. When using a Windows workstation for editing in the design I have found that the DELETE key is not available and I end up having to continually reposition and use the BackSpace key to remove unwanted lines or text.
2. In the IMAP4 Controls the listbox for Mailbox folders could be a bit wider for our purposes. We have to retain mail messages that we process and so use the mailbox folders to act as a library for processed messages and as such we need to nest to 2-3 levels deep to maintain readability. See ScreenShot
3. a visual aid in the package Design for me would be to be able to draw a box around a 1 or more action controls so that it can act as a shaded background colour for those controls - thus visually grouping them together. For Example you may have a set of controls that have a background shaded area of Green to indicate these are initialisation elements then another set coloured with a yellow background to indicate processing controls and then maybe a red section for outbound alerts for errors or failures.
4. Haven't thought this one through but perhaps TABS in the Package Designer similar to the TABS in the Transformation designer
5. Again in the Package Designer I often find that I am moving things around to see the very bottom if the Object selection toolbar. Especially when I am hunting for the Notes object which is at the bottom of the list. As you add more features and Action controls I suspect this list will become longer. I know you can use the Incremental Search but I personally prefer just seeing what I want and dragging it rather than typing and then dragging and dropping
6. My previous suggestion about Colour background for Package Notes
7. My previous suggestion for IMAP4 Extract Mask to handle multiple entries (possibly a RegEx)
8. Would still like to argue the benefits of an IMAP4 Event Monitor Filter
9. We still come unstuck with field mappings when making changes to a backend table (SQL Server) that is the source or target for a transformation and the shape of that
table changes. The transformation maps can get messed up when we change the backend table especially when delete fields . There is a suggestion we use a Transformation with the AutoMap turned on immediately for the writer and then place a transformation mapper in front of this to do all of the actual work. We have tried this but either don't follow what the suggestion was or are simply doing things wrong. But perhaps a Video tutorial on how to ensure that the field names are used rather than position and how to structure to minimise rework.
10. There are a few spelling mistakes on some key screens. Correcting these would give the product even more polish. For example the Maintain Grid has a typo in the 'CHANGED' column. There is also a Typo in the IMAP4 RECEIVE Control under the Advanced tab.
11. I don't believe this is currently available. But we could benefit from the ability to use the {} feature within a variable definition so that we could do something like TIMESTAMP-{GetSystemDate('YYYYMMDDHHNNSSZZZ')} which would result in a Variable Value of "TIMESTAMP-202001311309110001" . We currently do this via a Pascal Script Action within a Package but if we could do it within a Set Variable Action instead it would help cut down on the number of action Objects in the Package as we could group it in with a single Variable Set Action along with a few other Variables we use.
12. Is it possible to put a LOG Action into the Package Suite? I would use it as a runtime exception debugging and aid by recording certain variable and flow details into the log to compliment the internal logging.
13. We use Directory Connections quite a lot to keep the Transformation Reader and Writer paths very controlled. We also have a strategy of using a paths with names such as PENDING, PROCESSED and REJECTED with in a DEV, PROD and SIM parent folder across the whole ecosystem. This allows us to have the SERVER work in PROD and the Developers work in DEV or SIMulation by adjusting AETL global variables. Because of all of this it would be a benefit to us if somehow we could have File Operation Action Objects (and other relevant ones) provide not only the ability to browse to a folder but to also allow us to pick from a list of Connection Directory names rather than typing in <directory connection name>. The attached screenshot may make more sense.
Cheers
I believe is great value for money and very feature rich. With that in mind there are a couple of things that I come across when using it that I believe would be worthwhile enhancements
1. When using a Windows workstation for editing in the design I have found that the DELETE key is not available and I end up having to continually reposition and use the BackSpace key to remove unwanted lines or text.
2. In the IMAP4 Controls the listbox for Mailbox folders could be a bit wider for our purposes. We have to retain mail messages that we process and so use the mailbox folders to act as a library for processed messages and as such we need to nest to 2-3 levels deep to maintain readability. See ScreenShot
3. a visual aid in the package Design for me would be to be able to draw a box around a 1 or more action controls so that it can act as a shaded background colour for those controls - thus visually grouping them together. For Example you may have a set of controls that have a background shaded area of Green to indicate these are initialisation elements then another set coloured with a yellow background to indicate processing controls and then maybe a red section for outbound alerts for errors or failures.
4. Haven't thought this one through but perhaps TABS in the Package Designer similar to the TABS in the Transformation designer
5. Again in the Package Designer I often find that I am moving things around to see the very bottom if the Object selection toolbar. Especially when I am hunting for the Notes object which is at the bottom of the list. As you add more features and Action controls I suspect this list will become longer. I know you can use the Incremental Search but I personally prefer just seeing what I want and dragging it rather than typing and then dragging and dropping
6. My previous suggestion about Colour background for Package Notes
7. My previous suggestion for IMAP4 Extract Mask to handle multiple entries (possibly a RegEx)
8. Would still like to argue the benefits of an IMAP4 Event Monitor Filter
9. We still come unstuck with field mappings when making changes to a backend table (SQL Server) that is the source or target for a transformation and the shape of that
table changes. The transformation maps can get messed up when we change the backend table especially when delete fields . There is a suggestion we use a Transformation with the AutoMap turned on immediately for the writer and then place a transformation mapper in front of this to do all of the actual work. We have tried this but either don't follow what the suggestion was or are simply doing things wrong. But perhaps a Video tutorial on how to ensure that the field names are used rather than position and how to structure to minimise rework.
10. There are a few spelling mistakes on some key screens. Correcting these would give the product even more polish. For example the Maintain Grid has a typo in the 'CHANGED' column. There is also a Typo in the IMAP4 RECEIVE Control under the Advanced tab.
11. I don't believe this is currently available. But we could benefit from the ability to use the {} feature within a variable definition so that we could do something like TIMESTAMP-{GetSystemDate('YYYYMMDDHHNNSSZZZ')} which would result in a Variable Value of "TIMESTAMP-202001311309110001" . We currently do this via a Pascal Script Action within a Package but if we could do it within a Set Variable Action instead it would help cut down on the number of action Objects in the Package as we could group it in with a single Variable Set Action along with a few other Variables we use.
12. Is it possible to put a LOG Action into the Package Suite? I would use it as a runtime exception debugging and aid by recording certain variable and flow details into the log to compliment the internal logging.
13. We use Directory Connections quite a lot to keep the Transformation Reader and Writer paths very controlled. We also have a strategy of using a paths with names such as PENDING, PROCESSED and REJECTED with in a DEV, PROD and SIM parent folder across the whole ecosystem. This allows us to have the SERVER work in PROD and the Developers work in DEV or SIMulation by adjusting AETL global variables. Because of all of this it would be a benefit to us if somehow we could have File Operation Action Objects (and other relevant ones) provide not only the ability to browse to a folder but to also allow us to pick from a list of Connection Directory names rather than typing in <directory connection name>. The attached screenshot may make more sense.
Cheers
Last edit: 3 years 10 months ago by bruce.gibbins.
Please Log in or Create an account to join the conversation.
- Peter.Jonson
-
- Offline
- Platinum Member
-
- Peter.Jonson
-
- Offline
- Platinum Member
-
- Peter.Jonson
-
- Offline
- Platinum Member
-
- bruce.gibbins
- Topic Author
- Offline
- Platinum Member
-
3 years 9 months ago #19706
by bruce.gibbins
Replied by bruce.gibbins on topic AETLP Suggestions
Sure. maybe something like in the screen shot
Please Log in or Create an account to join the conversation.
