FieldLogs

1. Documents can be filtered based Custom Field values

Documents can now be filtered based on the values of the Custom Field Properties.  When you select Custom Fields in the dropdown, they are available as Filters as highlighted in yellow below.

You can then filter the documents based on the values of the Custom Fields. In the example below, the Custom Field test filter is used to filter documents. Values for the different fields are provided as highlighted below.

Documents are filtered based on the provided values.

2. Sharing Documents using a Public Link

You can share a file with someone using a publicly accessible link. You can send the link to the recipient, who can then click it to access the file.

You can also restrict public access to a file using a toggle button available on the document.

The green lock symbol highlighted below indicates that the file will not be accessible via the public link for an infinite amount of time. However, the file can still be accessed for around twenty to thirty minutes from when the link was shared. This can be used to share files for a short time.

Clicking the lock symbol makes the file available to be shared via a public link. This is indicated by an open red lock symbol shown below. Using the public link, the file remains accessible for an infinite amount of time.

1. UX Improvement in Entering Values

While executing a Task on the web, there is now a pop-up displayed to accept numeric or text values on Steps. This feature eliminates the possibility of scrolling down without saving the values entered.

2. UX Improvement for Step Navigation

There is now a Go to Step button available on the web while executing a Task.

You can enter the Step number to go to in this input box.

1. Operation Plan with Counter Process Lifecycle

You can now create Operation Plans of type Lifecycle and Action.

This allows you to associate a process with the Operation Plan. The process is defined as a Lifecycle. The Templates that are part of the process are defined in the Actions section as shown below.

When the Operation Plan is executed, the process specified in the Lifecycle is carried out. Accordingly, Tasks are generated from the Templates. Users can then execute these Tasks.

1. Role-based Visibility to Documents

It is now possible to restrict access to documents based on User Roles. Further, access can be granted to documents in a specific status - Draft, Approved, or Deleted.

Depending on the requirement, you have the following options available.

2. View Task Information from Raised Incidents

From the Incident Details popup, it is now possible to view the Context from which the Incident was raised, for example, the Task related to it.

Clicking View brings the user to the Task related to the Incident. Clicking View Info displays information about the Task.

3. Step Conditions Based on Validated Signatures

A new Step Condition based on Validated Signatures is now available in the Step Condition Accelerator. Steps can be hidden/shown and made active/inactive based on whether a Step has a validated signature or not. This is available only on Steps that have a Sign Off.

4. Task Assignment Registered in Task History

When you Push to My inbox or Push to User inbox from the Planning section, it is now registered in the Task assignment history.

5. Displaying Steps in a Continuous Sequence after Applying Effectivity

For Templates with Dynamic Numbering enabled, the Dynamic Numbering (highlighted in yellow below) appears alongside the Step Numbers.

After applying Effectivity during Task Execution, the applicable Steps will appear in a continuous sequence. This improves user experience during Task Execution.

For example, here a Dynamic Numbering of A,B,C,D,E are applied to the Steps.

When an Effectivity of Tail Number 55 is applied, only steps D and E are applicable. Hence the steps D and E get dynamically numbered as A and B to appear in a continuous sequence.

1. Lock/Unlock Steps to Prevent Simultaneous Multiple Editions

When one version of a Template, say 2.0, is submitted for Edition, the Template is locked until that Edition is complete. If another version, say 3.0 is submitted for Edition before the Edition of 2.0 is complete, then version 3.0 enters a Wait state. Version 3.0 can only be resumed after the Edition of version 2.0 is complete, archived or terminated. This is depicted below.

Additionally, an admin level. Unlock button can be used to resolve any contention and allow the progress of another Edition.

2. Rejection of one Review Tasks Cancels the others in a Parallel Review

When multiple reviews of a document happen in parallel, the rejection of one of these reviews triggers the deletion of all other open review tasks. Even if some of the reviews were approved before the first rejection, the overall result of the Parallel review will remain rejected.

3. Part numbers in Configurations can be sorted in View Mode

It is now possible for the user to sort the Part numbers in the Configuration matrix in a Published Template (View mode) too. Part numbers can be sorted in either ascending or descending order.

When the Part numbers are initially added to a Configuration matrix, they are added in ascending order by default.

4. Quality Validation Rules can now include checks on Functional Types

Functional Type values can now be used to validate Templates. There is a new option Functional Type that can be selected while creating Quality Validation Rules.

Standard string comparison operators are available to check the values of Functional Types while validating a Template.

5. Step Filters now include Custom Sequence and Step ID

The Step Filters available on the Template can now filter Steps based on Custom Sequence and Step IDs.

1. Sending Emails from A Lifecycle

It is now possible to send emails from within a Lifecycle using scripts. The script can send emails to stakeholders who are not required to take any action, but need to be informed about the progress made.

2. Improved User Experience in the Inbox UI

In the Inbox UI, the order of the options “View” and “Continue” available on a Task have been reversed for a better user experience. This prevents users who want to view the Task from inadvertently clicking “Continue”.

Now, the option “View” appears first, followed by “Continue” on Tasks in the Inbox. This is shown in the screenshot below.

3. Templates with Documentation References added from the OEM Manual now Covered by Screening

You can now add Documentation References from an OEM Reference Manual at the Template level. Earlier, it was possible to add them only at the Step level.

To add a Documentation Reference from an OEM Reference Manual to a Template, open the Reference Manual and click the Add Documentation Key to Template option as shown below.

The Documentation Reference is then added to the Template as shown.

4. Improved UI Layout for Efficient Screening

The Screening UI now has a new comprehensive layout for an enhanced user experience. The minimalist UI clearly lists the Template Hits and OEM Hits in a tabular format. Each Hit is presented as a row in the table, with the Page Block, Affected Area, Description, OEM Change Flag and the FieldLogs Change Flag. The Status of the Hit is displayed. The last column has options to pre-screen and view the impacted content.

The screenshot below shows the improved layout. The columns can be re-arranged if required.

You can now add multiple comments against an Impact as shown below. For each Hit, you can click the pop-out icon to view the detailed description, screening flags, Configuration details and the comments left on the Hit.

5. A fresh look for the Template Library Pane

The library pane available in the Templates Authoring Page now has a new look and added features. This new Template organization has a search bar, filters and a section that displays recently accessed Templates. The Templates Under Edition will also be covered in the search. You can also save your searches to reuse them.

You can choose to turn this new interface On or Off in the Enterprise settings under the Profile tab. The Use new Template UI option can have the value On or Off. By default, it is Off.

6. Custom Actions Triggered during Template Creation to set Different Attributes of Templates/Steps

While creating a Template, you can trigger some Custom Actions to set values of Template and/or Step attributes based on user input. When you click the “New” button to create a Template, a pop-up appears as shown below. You can input values for the fields.

Currently, the following inputs are accepted during Template creation:

The properties that can be set based on these inputs are:

This feature is turned ON at request. Please speak to your Project Lead to turn this feature ON.

7. Filtering by Effectivity passed from the Operation Plan to Tasks

Effectivity Asset Status Variables added as Variables in Operation Plans can be linked to Template Variables. This makes the Filtering of Steps by Effectivity reflect from the Operation Plans to the Tasks during web execution.

8. API to return the Documentation Keys of a Template

The API to retrieve the details of Templates now returns all the Documentation Keys associated with the Template. If there are none associated, a null value is returned.

1. New keywords available for Template Scripting

FieldLogs Keywords can be used in Template Scripts to manipulate or retrieve FieldLogs specific data. These keywords can be identified with the prefix "Flkw". They can be used with JavaScript Instructions. Some of these Instructions require values to be provided as input parameters. The Script interacts with the data of the current Task and performs an action or returns the required information.

The recently added FieldLogs Keywords (Flkw) along with their corresponding input parameters are as follows:

2. User Experience Improvement in the Template Authoring Screen

The library pane in the Template Authoring Screen can now be resized manually or completely collapsed to suit the author’s preference.

3. Camera Captures can be added to Step Logs

Pictures, audio, and video captured using the device camera can be added to Step Logs while executing a Task.

4. Support for Baseline and Screening Service Bulletins (SBs) in S1000D

As part of the ongoing support for Service Bulletins in S1000D, it is now possible to create a Baseline of a new SB. Revisions to the SB can be screened, and impacts will be highlighted to enable the document screener to take appropriate action. The impacts will have the OEM Change Type and the FieldLogs identified Change Types populated.

5. API to create Operation Plans containing Multiple Task Done Trigger

The API that is used to create Operation Plans now supports Multiple Task Done Trigger as well. Using a POST call, the Operation Plan can be defined using a JSON file that contains a new section for Multiple Task Done trigger. This is available on both individual tasks and task queue selection.

1. Attaching Files while Raising Incidents

You can now add more information while raising an Incident by attaching files to it. Multiple files can be attached to a single Incident.

2. New Triggers based on the Progress of Tasks

Two new Triggers are now available on Operation Plans.

3. New Pre-Screening Flag for Content Updated by an Incremental Change (IC)

A new pre-screening flag Already Incorporated by an IC is now available while screening Hits. Changes to the baseline of the manual that were done by an IC will have this flag set. This ensures that the changes already done by an IC do not show up as new Hits again while screening a full revision. These changes can then be bulk marked as screened or pre-screened.

4. Steps filtered based on Configurations and Step Text

There is a new filter available on Templates that lets you filter the Steps of the Template based on Step Title and Configurations.  

To filter based on Configurations, click the filter icon corresponding to the required Configuration.

You can filter the Steps based on the Step text as shown below.

5. QR Code Generation in PDF reports

PDF reports can now generate QR codes based on specified data. This provides a convenient way to quickly access information related to the data in the reports quickly. For example, a QR code may be generated from a combination of Suite, Package, and Template Title. This can be included on every page of the report, for the technicians to have quick access to this data.

 The Incident Management System enables users to track operational Incidents. When an Incident is raised, it initiates a set of predefined actions to resolve it. 

The Incident Dashboard displays all the Incidents raised in the system. Users with the required access privilege can view the Incident and initiate the necessary action.

Every Incident is configured by the Administrators using the Incident Definition page shown below.

The set of steps to resolve the Incident is built into a Custom Lifecycle of type Incident as shown below. This Custom Lifecycle is defined before the Incident is defined, and set as the Resolution Flow.

New Effectivity rules have been added as part of the enhanced features to support SGML Service Bulletins (SBs). Referenced Effectivity rules can be set based on the SB Configuration, Serial Number List, SB Configuration Number and SB Configuration Range.

You can now configure Manual Describers to send out email notifications. This can be used to remind your OEM team to check for available revisions to the manual proactively. You can specify the frequency in which emails are to be sent.

Referenced Effectivities present in Components can now be evaluated during runtime and report generation from the parent Template. With this improvement, the evaluation of Referenced Effectivities is seamless between the Steps in the parent Template and the Component.  

In the example below, note the Referenced Effectivity highlighted in the Component Step 2.2.

This Referenced Effectivity can be evaluated from the parent Template at runtime as highlighted below.

The Template Configurator is no longer tied to just Part Numbers. You can create your list of possible Configurations. The user can configure Components based on the Configurations of the parent Template.

A new admin page for Enterprise Variables allows you to create, modify, and delete Enterprise Variables.

The page lists all the available Enterprise Variables in the system.

You can override Component Variables with Variables from the Template/Step that contains the Component. The Component Variable can be linked with the Template/Step Variable using the + Add Variable link option shown below. The Source Variable from the Template/Step can be linked to the Target Variable from the Component.

The Technical Publications Search filter now has the following improvements.

In the Batch Operations modal dialog, there is now a new Download button, that is displayed when the Batch Operation is complete. You can download the reports by clicking this button. It is no longer required to navigate to the Batch Operations page to download the reports.

Quality Validation Rules on Modules can now be linked to Lifecycles.

When a Module published using such a Lifecycle is under Edition, the Rules can be Validated.

It is also possible to prevent publication of the Module if the validation of rules fails.

Functional Types are a great way to add visual indicators to a Template. We have now added an option to re-order the list of Functional Types, so you can save the Functional Types in the required order for easy access. . A Reorder button is available on the Functional Types page as shown below.

The list of Functional Types can be re-ordered in ascending or descending alphabetical order. It can also be saved in a customized order, by dragging the Functional Types to the required position.

To know more about these enhancements, click here.

Screening has now been enhanced to highlight the Steps in the Template impacted by the revision. The screening user can then focus on the highlighted Steps and take the required action.

When the user selects and views a Match Impact, the Template is displayed in Read-Only mode, and the impacted Steps are highlighted, as shown below.

Templates containing multiple levels Steps now have an Expand/Collapse option available. This allows users to view the Template at the required level of depth easily.

The Enterprise Administrator can now configure any valid email ID as the Apps support email ID in FieldLogs. All Apps help requests are then directed to this email id, which serves as the Apps initial support contact.

The Publication Action of the LifeCycle can now be bound to an External Identity If a user signs in to an External Authentication account while logging into FieldLogs, as shown below, the external identity is linked to the user acount.

This feature ensures that only the Publish action is disabled, if the required external identity has expired or is not present when the user logs in.

To bind the Publish action to the identity, the Require Identity option, available on the Publish action is checked. The identity tied to the action is selected from the Identity dropdown as highlighted below.

If the configured identity is absent, the Publish option appears disabled as shown below.

FieldLogs now supports a new View Only role type for Templates.

A user with this role can view published Templates. A user with this role:

The role is configured as seen below.

The user cannot access the Templates Under Edition as seen below.

The description of a Module Library will now be displayed along with the name in the property pane of the Template into which it is inserted. This provides additional information about the inserted Module Library.

The description and name will be displayed in the property pane, as shown below.

It is now possible to have a default assignee when an Operation Plans is defined. Earlier, it was not possible to assign the complete Operation Plan, although the Tasks generated by the Operation Plan could be assigned.

The default assignee can be set in the Operation Plan Definition dialog, as shown below.

The default assignee can be changed while Instantiating an Operation Plan, as shown below.

The assignee can also be changed at the Planning stage as shown below.

You can also change the assignee during execution. This can be done using the Edit Operation Plan option in the Planning section, as shown below.

Grouping displays Tasks based on selected criteria. You can now save and bookmark your Custom Groupings in Planning, using the option highlighted below.

These bookmarked groupings can be accessed from the Group by dropdown below.

QR codes have been introduced to make Task Sharing quicker and easier.

Field workers can generate a QR code for a Task, or any Step in a Task, using the QR Code option from the Task or Step contextual menu, as shown below.

The corresponding QR code is generated as shown below.

Using the highlighted Scan option below, a co-worker can scan the code on a different device.

Multiple options are presented to the user when the QR code is scanned.

The selected Task or Step is highlighted and the co-worker can now perform the required action.

When a Template is submitted for Edition or a new version is initiated, the user can now choose to directly view the Template Under Edition, without having to navigate to the tab.

This option opens the submitted Template in the Templates Under Edition tab.

The Planning Page has been improved to optimize the screen layout. Task Filters have been organized into a separate panel leaving more space for planning information.

When a Task or Operation Plan is selected, the corresponding options appear in a separate panel on the right. The user can create, edit, or archive Tasks from this panel. New Operation Plans can also be created.

A text filter is now available to search through the Custom Field library for specific Custom Fields. It returns Custom Fields whose names contain the entered text. This is a more efficient way to search through long lists of Custom Fields.

Additionally, the Delete option for Custom Fields has been enhanced to offer a reversible Decommission option. Decommissioning allows you to prevent a Custom Field from being used in the system. A Decommissioned Custom Field can be restored if required.

To know more about these enhancements, click here.

Planners can mark Tasks as critical using a toggle button, indicated below. Critical Tasks are highlighted in red.

Switching on the Critical Path toggle button displays all the critical Tasks.

To know more about these enhancements, click here.

Using the Edit Multiple-Steps option, you can now create Step Conditions and apply them to a selection of Steps in a Template. When the Condition is met, all targeted Steps are rendered Active, Inactive, Hidden or Visible, as the case may be.

This ability to apply a Step Condition to multiple target Steps avoids the need to repeat the Step Condition for every target Step.

The search results of Standard Steps can now be sorted by name or Id, using a dropdown box highlighted below. These sorting options are very useful while working with Templates containing several Standard Steps.

The Template Diff Feature helps users during Screening and Template Edition to easily compare two versions of the same Templates. They can apply differences selectively from one Template to the other.

Now, with the newly added filters, the list of differences can be narrowed down. For example, you can filter the search results to display only the differences in Signoffs or Step Types between the two Templates.

The Step/Template toggle below switches views to display Template-level and Step-level differences.

An option to generate a Template from the Reference Manual from within the Template Diff screen has also been added.

The Matched Impacts under Bundle Tasks can now be grouped by Functional Types. This filtering would make it easier to check for a single Template, especially when there are multiple pages in the Bundle Tasks.

Functional Types can now be used in Operation Plans and their Counters. These Functional Types will be associated with all the Tasks created by that Counter.

In the Inbox and planning sections, the Functional Types help us easily identify the Tasks from an Operation Plan.

Custom Fields can now be composed of multiple fields. This is very useful when other systems interacting with FieldLogs use fields composed of more than one field. For example, we could have a single Custom Field Flight Details composed of two fields Departure details and Arrival details.

The Technical Publications Search, referred to as Tech Pub Search, is a search option in FieldLogs to search through the content of all the Reference Manuals in the system. The user specifies a search keyword. The system then performs a simple text search across all the Reference Manuals and returns the matching results in order of relevance. To learn more about Tech Pub Search, click here.