Stimulsoft Reports.Web

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Stimulsoft Reports.Web is a .NET based reporting application designed for creating and rendering reports on the Web. This technology provides the complete cycle of report development, from beginning with creating report templates, and ending with showing those reports in a web browser. Stimulsoft Reports.Web also allows a user to edit reports directly on the Web. This technology has the ability to get data from the following data sources: Microsoft Structured Query Language (SQL) server, Oracle Database, PostgreSQL, SQLite, Open Database Connectivity (ODBC), or Object Linking and Embedding Database (OLE DB). Users can also get data from Extensible Markup Language (XML) files. This technology may be utilized on a Windows Desktop, Tablet, Smartphone, or Web Browser. This entry covers the Desktop Edition of this technology and not any mobile versions. Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and approved by the Mobile Technology and Endpoint Security Engineering Team: http://vaww.eie.va.gov/SysDesign/CS/MT/default.aspx
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v22.9
Decision Date:	09/21/2022 at 02:03:45 UTC
Introduced By:	TRM Request
Vendor Name:	Stimulsoft

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
2011.1	04/04/2011
2011.2	09/19/2011
2011.3	12/01/2011
2012.1	04/12/2012
2012.2	09/20/2012
2012.3	12/04/2012
2013.1	04/04/2013
2013.2	10/01/2013
2013.3	12/03/2013
2015.1	04/16/2015
2016.x	02/19/2016
2017.x	04/27/2017
2018.x	12/01/2017
2019.x	12/18/2018
2020.x	12/19/2019
2021.x
2022.x

Current Decision Matrix (09/15/2022)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2017

CY2018

CY2019

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

2011.1

Unapproved

2011.2

Unapproved

2011.3

Unapproved

2012.1

Unapproved

2012.2

Unapproved

2012.3

Unapproved

2013.1

Unapproved

2013.2

Unapproved

2013.3

Unapproved

2015.1

Approved w/Constraints
[1, 2, 3]

Divest
[1, 3, 4]

2016.x

Approved w/Constraints
[1, 2, 3]

Approved w/Constraints
[1, 3, 4]

Divest
[1, 3, 4]

2017.x

Unapproved

Approved w/Constraints
[1, 3, 4]

2018.x

Unapproved

Approved w/Constraints
[1, 3, 4]

2019.x

Unapproved

2020.x

Unapproved

2021.x

Unapproved

2022.x

Unapproved

Decision Constraints


[1]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[2]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[3]	Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities.

[4]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

Note:

At the time of writing, version 2022.3.5 is the most current version.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
Vendor Provided*	Documentation		This website links to the user guides for this technology.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
StiMobileDesigner, StiMvcMobileDesigner	These are unique Active Server Pages (ASP) .NET components for designing reports in a browser. The report designers are built using Hypertext Markup Language (HTML) technology and do not require the installation of additional modules in the web browser.
StiMobileViewer, StiMvcMobileViewer	The components are specifically designed for viewing reports on mobile devices such as smartphones and tablets. They display reports using the browser installed on a mobile device. The components also can display reports for desktop computers and laptops. The component for Active Server Pages (ASP) .NET is StiMobileViewer. The component for ASP.NET Core Model-View-Controller (MVC) is StiMvcMobileViewer.
StiWebDesigner, StiMvcDesigner	These are components with fully featured report designers for Active Server Pages (ASP) .NET. The report designers are created using the Adobe Flash technology. When calling the ASP.NET page that hosts the component, the Flash report designer is loaded on the client side. After loading, the report designer requests all the necessary information from the page which it was loaded from. Using this component is maximally automated and simplified. The report designer has an intuitive interface and a large number of solutions for working with reports. The component for ASP.NET is StiWebDesigner. The component for ASP.NET Core Model-View-Controller (MVC) is StiMvcDesigner.
StiWebViewer, StiMvcViewer	The components are used to view reports. Ease of use is combined with a wide range of methods for working with the report and a large range of supported standards and technologies. These components are the best for inclusion in web applications that are used to display information on desktop computers and laptops. The component for Active Server Pages (ASP) .NET is StiWebViewer. The component for ASP.NET Core Model-View-Controller (MVC) is StiMvcViewer.
StiWebViewerFx, StiMvcViewerFx	The Active Server Pages (ASP) .NET components are used to display reports. They can be implemented for viewing reports in a web browser using the Adobe Flash technology.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Information Management Technologies Business Intelligence and Data Warehouse Platforms	Web Reporting Tools

Operating Systems Supported by the Technology

macOS - Approved w/Constraints
Red Hat Enterprise Linux (RHEL) - Approved w/Constraints
Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This technology can export reports in various formats and enables printing reports as images. This technology supports Forms Authentication.
Users can implement a login view that will take input (login and password) from the user, post it back to the controller to authenticate credentials, and then redirect request to appropriate view.
This is a mature technology.

Adoption Risks

There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.nist.gov/vuln/search for more details.
This technology can integrate with and alter database technologies.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
This software has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
The technology requires the purchase of licenses from vendor, which could potentially lead to vendor lock-in.
This technology can potentially use Adobe Flash Player, a prohibited technology.
This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms.

Architectural Benefits

This technology can support the data fetching from various VA approved data sources. Data can be processed with grouping, sorting, filtering, and joining prior to report generation.
This technology is portable as it runs on multiple TRM-approved operating systems.
This technology can use a VA-preferred database.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (09/15/2022)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (09/15/2022)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

EMAIL UPDATES