Access to AWS Blu Insights is limited to AWS Blu Age practitioners who are working on modernization opportunities, AWS Blu Age customers, and certified individuals with the AWS Refactor Accreditation Program. This latter is based on three complementary levels of certifications. Each level grants access to different services.
With AWS Blu Insights, you break up your work into separate projects. Each project contains everything related to the work at hand; all the people involved, every document, file, task, important dates, etc. Everything! Unlike email where everything starts disorganized and you have to constantly manage the chaos, AWS Blu Insights projects keep everything organized by default. Things are always where you expect, and it’s obvious where to put stuff.
Every project includes the tools all teams need to work together; Assets, To-Dos, Schedule, Documents, Management, and Catch-up. You can turn off the ones you don’t need to tailor things to the project at hand. Spreading work across a bunch of apps is inefficient, expensive and onboarding your team is a pain. AWS Blu Insights eliminates all of those issues by combining everything you need in one place. It’s “easy mode” for work.
Start by creating a demo project or your own project in order to discover all the features of AWS Blu Insights.
To create a demo project, you can choose from our four different technologies in the Codebase section:
To create your own Codebase project, just click on the +New button:
You can also create a To-Dos project by going to the To-Dos section.
The To-Dos type allows you to collaborate, manage projects, and organize tasks. It’s packed with all the features to help your team succeed. From boards and documents to events and timelines, AWS Blu Insights features give your team the power to quickly set up workflows and meet deadlines.
In addition to the power of the todo project, the Codebase project type provides a complete code management package, from uploading source code resources to exploring insights, planning the project, and testing.
On the home page, you will also find the list of all the projects you have visited recently. The first project in this list is the last one you have visited. You can clean this list at any time by clicking the trash can icon.
The activities of your team are available in the activities feed. They correspond to the activities of the project you have currently selected. The activities can be filtered.
AWS Blu Insights access is possible directly from the AWS Console. Users will get direct access to AWS Blu Insights from the console using their AWS accounts. To do so, they have to follow these steps:
AWS Blu Insights will associate your email to the AWS account.
For more details, check the FAQ.
To invite members (customers, partners, colleagues…) into your projects, head to the people page of a project. You’ll see the option to invite a client to the project:
Enter the complete email of the client and click on “Add another person”. Registered members will be visible on the table and non-registered ones will be listed on the invitation tab. Once registered they will automatically be listed on the first tab. All invited members will receive an email to register and/or connect to AWS Blu Insights so they will be able to see the project.
Different permissions can be granted to invited members depending on their roles. These permissions are grouped into Profiles and are managed at 4 levels:
If Codebase projects are created from a Secured Space, download authorizations can be deactivated by the owner of the Secured Space.
By default, a AWS Blu Insights project is built within 3 profiles
Modules are managed at the project level and the profiles are automatically updated accordingly (See Settings)
Denying a member access is more useful than deleting him from the project to keep the history of their contributions (comments, documents, etc..).
To deny access to members, select them and click on Deny Access.
To grant them access again to the project, select them and click on Grant Access.
Owners of the project controls downloads authorizations among all team members.
You can only download documents which are directly shared with your profile (or contained in a shared folder). Profiles are managed on the People page of your project.
When you see 404 page, it means something has gone wrong. Among the reasons, it can be that:
As a modernization project point of contact and user of AWS Blu Insights, you can follow this process to get the codebase from your customer:
We list in this page a few guidelines and expectations regarding the assessment baseline.
AWS Blu Insights can extract a suitable codebase from special formats, such as:
Depending on the project (customer requirements, legacy technologies, etc.), different types of test cases can be required.
See Test Capture & Replay for TN3270 and TN5250 to see how AWS Blu Insights can automate the definition of these test cases.
Database extractions for the Tables in related to the POC migration
For Project migration, all the used Tables will be extracted.
Please read carefully and check the pre-requisites. Access approvals need up to 24 hours to be processed.
The success of an AWS Blu Age modernization project starts with a tight collaboration between experienced L3 Certified individuals (L2 Certified could be involved in the assessment phase) and the final customer. To use AWS Blu Insights, as explained during the training program, you need to follow the workflow described below.
To filter your data in an easy and powerful way, we designed our own query language: AWS Blu Insights Query Language (BQL).
Just type your BQL query in the filter field displayed on top of almost every page.
This section describes information about fields that are used for searching. A field in BQL is a word that represents a AWS Blu Insights artifact. In a statement, a field is followed by an operator, which in turn is followed by one value or a regular expression (regex). The operator compares the value of the field with the value on the right, such that only true results are retrieved by the statement.
|Type||Supported operators||Value types||Examples|
|string||String with single or double quotes|
would result in all files with names starting with disc
|Array of strings with double or single quotes|
would result all workpackages in Workpackage1 or Workpackage2
would result all workpackages in Workpackage1 and Workpackage2 at the same time
|date||date formatted like YYYY-MM-DD or YYYY/MM/DD|
An additional operator is Empty is available for every types. This operator works without value type, e.g. name is empty.
|homonym types||has the value ‘identical’ if the file has identical homonyms||string||Assets > Homonyms|
|indegree||Number of ingoing edges (parents)||number||Assets > Dependencies|
|link type||string||Assets > Dependencies|
|node type||string||Assets > Dependencies|
|number of comments||number||Assets|
|number of labels||number||Assets|
|number of workpackages||number||Assets|
|outdegree||Number of outgoing edges (children)||number||Assets > Dependencies|
|number of labels||number||To-Dos|
|number of workpackages||number||To-Dos|
|entry points||number of entry points (indegree = 0 and outdegree > 0)||number||Management > Workpackages|
|number of CI/CD jobs||number||Management > Test Scenarios|
|number of issues||number||Management > Test Scenarios|
|number of labels||number||Management|
|number of workpackages||number||Management|
|nb batches||number of batches||number||Pipeline|
|nb reports||number of reports||number||Pipeline|
|nb screens||number of screens||number||Pipeline|
|nb transactions||number of transactions||number||Pipeline|
|number of legacy database||number||Pipeline|
|number of partners||number||Pipeline|
|poc/pilot total line of code||number||Pipeline|
|total duration (in month)||number||Pipeline|
|total line of code||number||Pipeline|
The “=” operator can be used with ‘uncategorized‘ like workpackage = ‘uncategorized’. This operation is similar to workpackage is empty. The fields available are Workpackage, Status and Label.
To build even more complex filters, you can use logical operators “and” and “or”. You can also use parentheses to group your conditions. Thus, you can build powerful filters such as:
(name like '\\.CBL' and workpackage in ['WP1', 'WP2']) or start date between 2021/04/10 and 2021/04/25
Saved searches are shown on the left side of the advanced search input. Click on the “filter” button on the left side of the search input to display it.
To run a filter, e.g. Epics, simply click it. The BQL for the search will be set, and the search results will be displayed.