A leading publishing company
12 weeksvs. 12 months originally estimated
SIARASmartView Intelligent Analysis, Review & Automation
Cut months of migration efforts to weeks.
An agentic solution for your entire SmartView application. SIARA coordinates the specialist skills. Your team guides the work with Ask SIARA.
A plan shaped around your application
The right skills.
For your requirements.
SIARA turns analyzed features into a delivery plan, selecting relevant skills, connecting the work and bringing decisions to your team.
See the decision behind the work.
One shared report form or a separate form for each document type? SIARA makes the choice visible and maps the skills needed for each path.
Your team reviews the direction before moving forward.
400+AI agents & skills under the hood.
Selected to fit the work.
Explore a sample workflow
Selected to fit the work.
A decision for your team
Do the report types share a base document type?
Yes
Configure one shared query formD2 search configuration
No
Configure a query form per typeD2 search configuration
Explore the full sample workflow 3 features · 20 planned steps
The actual SIARA workflow canvas
Explore the saved Corvane Energy demo plan. Select a feature, inspect its steps or enlarge the diagram.
Generated workflow
Enlarge ↗
Run a document status report
7 planned steps2 distinct skills2 decisions
From the analyzed feature
- The CCD, Engineering, Forecast, Reason for Issue, RFI and Vendor reports each filter one document set.
- Date-range reports need both dates, inclusive, with To not before From.
- Reports cover all versions.
- Each report becomes a D2 query form.
Step details
Decide whether the report types share the base document type
Human decision
Decide whether the report types share the base document type
Planned output
Choice between one shared query form and one form per type
Depends on
- Feature requirements from Analysis; no earlier step dependency in the saved plan.
Branches in this plan
Yes: Configure one shared query form on the base document type
No: Configure one query form per report type
Decision pending. This website does not choose or approve a branch.
Configure one shared query form on the base document type
D2 search configuration
Configure one shared query form on the base document type
Planned output
One D2 query form on the base document type (all versions) with a report-type criterion and bound date and filter criteria
Depends on
- Decide whether the report types share the base document type
Planned work from the saved draft. This is not a completed build step or a test result.
Configure one query form per report type
D2 search configuration
Configure one query form per report type
Planned output
Six D2 query forms, each on its own type, all versions, with bound criteria
Depends on
- Decide whether the report types share the base document type
Planned work from the saved draft. This is not a completed build step or a test result.
Decide whether query forms can enforce the date rule
Human decision
Decide whether query forms can enforce the date rule
Planned output
Choice between native validation and a custom guard
Depends on
- Feature requirements from Analysis; no earlier step dependency in the saved plan.
Branches in this plan
Yes: Configure native criteria validation
No: Build a custom date-range guard for the query forms
Decision pending. This website does not choose or approve a branch.
Configure native criteria validation
D2 search configuration
Configure native criteria validation
Planned output
Query forms requiring both dates and rejecting To before From
Depends on
- Configure one shared query form on the base document type
- Configure one query form per report type
- Decide whether query forms can enforce the date rule
Planned work from the saved draft. This is not a completed build step or a test result.
Build a custom date-range guard for the query forms
Custom work
Build a custom date-range guard for the query forms
Planned output
Client-side guard blocking Generate when a date is missing or To is before From
Depends on
- Configure one shared query form on the base document type
- Configure one query form per report type
- Decide whether query forms can enforce the date rule
Planned work from the saved draft. This is not a completed build step or a test result.
Verify the reports in SmartView
SmartView acceptance verification
Verify the reports in SmartView
Planned output
Evidence that each report returns its document set across all versions, applies the date rules and binds its criteria
Depends on
- Configure one shared query form on the base document type
- Configure one query form per report type
- Configure native criteria validation
- Build a custom date-range guard for the query forms
Planned work from the saved draft. This is not a completed build step or a test result.
Generated workflow
Enlarge ↗
Page, reset and export report results
9 planned steps5 distinct skills2 decisions
From the analyzed feature
- Results show in a paged grid that can be reset or closed.
- Export is allowed only after Generate and writes the configured columns.
Step details
Configure the paged results list
SmartView result list
Configure the paged results list
Planned output
Paged SmartView result list for the query-form results, with reset and close
Depends on
- Feature requirements from Analysis; no earlier step dependency in the saved plan.
Planned work from the saved draft. This is not a completed build step or a test result.
Decide whether Forecast columns follow the export fields
Human decision
Decide whether Forecast columns follow the export fields
Planned output
Forecast column rule
Depends on
- Feature requirements from Analysis; no earlier step dependency in the saved plan.
Branches in this plan
Yes: Align Forecast grid columns with the export fields
No: Configure separate Forecast grid columns
Decision pending. This website does not choose or approve a branch.
Align Forecast grid columns with the export fields
D2 document list configuration
Align Forecast grid columns with the export fields
Planned output
Forecast grid columns matching the export column set
Depends on
- Configure the paged results list
- Decide whether Forecast columns follow the export fields
Planned work from the saved draft. This is not a completed build step or a test result.
Configure separate Forecast grid columns
D2 document list configuration
Configure separate Forecast grid columns
Planned output
Forecast grid columns that are kept separate from the export column set
Depends on
- Configure the paged results list
- Decide whether Forecast columns follow the export fields
Planned work from the saved draft. This is not a completed build step or a test result.
Decide whether SmartView 26.2 exports natively
Human decision
Decide whether SmartView 26.2 exports natively
Planned output
Native or custom export path
Depends on
- Feature requirements from Analysis; no earlier step dependency in the saved plan.
Branches in this plan
Yes: Enable native export on the results list
No: Build a streamed Excel export REST extension
Decision pending. This website does not choose or approve a branch.
Enable native export on the results list
D2 document list configuration
Enable native export on the results list
Planned output
Native export of the configured columns, available after a query has run
Depends on
- Align Forecast grid columns with the export fields
- Configure separate Forecast grid columns
- Decide whether SmartView 26.2 exports natively
Planned work from the saved draft. This is not a completed build step or a test result.
Build a streamed Excel export REST extension
SmartView REST extension
Build a streamed Excel export REST extension
Planned output
Authenticated REST endpoint that re-runs the bound query and streams an .xlsx of the configured columns
Depends on
- Align Forecast grid columns with the export fields
- Configure separate Forecast grid columns
- Decide whether SmartView 26.2 exports natively
Planned work from the saved draft. This is not a completed build step or a test result.
Add the Export to Excel command
SmartView command
Add the Export to Excel command
Planned output
SmartView command, enabled only after Generate, that downloads the export
Depends on
- Build a streamed Excel export REST extension
Planned work from the saved draft. This is not a completed build step or a test result.
Verify paging, reset, close and export
SmartView acceptance verification
Verify paging, reset, close and export
Planned output
Evidence that paging, reset, close and export of the configured columns work, and that no file is left on the server
Depends on
- Configure the paged results list
- Enable native export on the results list
- Add the Export to Excel command
Planned work from the saved draft. This is not a completed build step or a test result.
Generated workflow
Enlarge ↗
Restrict reports to admins
4 planned steps3 distinct skills0 decisions
From the analyzed feature
- Only administrators users see the reports, through a context and matrix binding.
Step details
Create or reuse the administrators context
Custom work
Create or reuse the administrators context
Planned output
D2 context limited to administrators members
Depends on
- Feature requirements from Analysis; no earlier step dependency in the saved plan.
Planned work from the saved draft. This is not a completed build step or a test result.
Bind the report query forms to the administrators context
D2 matrix configuration
Bind the report query forms to the administrators context
Planned output
Matrix cells enabling the report query forms only for the administrators context, with other cells unchanged
Depends on
- Create or reuse the administrators context
Planned work from the saved draft. This is not a completed build step or a test result.
Add the Reports entry to the admin Smart Menu
D2 Smart Menu
Add the Reports entry to the admin Smart Menu
Planned output
Reports menu entry visible only to administrators
Depends on
- Create or reuse the administrators context
Planned work from the saved draft. This is not a completed build step or a test result.
Verify reports are hidden from non-admins
SmartView acceptance verification
Verify reports are hidden from non-admins
Planned output
Evidence that administrators users see and run the reports and other users do not
Depends on
- Bind the report query forms to the administrators context
- Add the Reports entry to the admin Smart Menu
Planned work from the saved draft. This is not a completed build step or a test result.
The same workflow canvas used in SIARA, showing a saved AI-generated plan in read-only mode. All 20 steps and their stored dependencies are preserved across these three features. Customer-specific names are generalized; internal prompts, source paths and implementation instructions are omitted. The plan is a draft, not evidence of an executed build or passed tests.
Ask SIARA
Your expertise.
Part of the process.
Your team knows the business. Ask SIARA helps you bring that knowledge into the findings and the delivery plan.
- Refine the findings.Request corrections and reorganize features. SIARA checks proposed corrections against the source code.
- Shape the plan.Ask why a step is needed or request a change to a feature, step or feature set.
- Choose what changes.Review proposals before applying them. Applied changes can be undone.
Ask SIARA
Feature set · Document numbering
Your request
Separate generating a document number from locking the document name.
Proposed changes
Split the existing feature into two focused capabilities.
Generate the document number
Keep the numbering rules together.
Lock the document name
Make the naming restriction explicit.
Awaiting your review. Nothing has changed.
Illustrative interaction showing the review controls. No live project is connected; buttons affect this example only.
AI moves the work forward.
Your team decides what moves ahead.
From reviewing findings to refining the plan with Ask SIARA, your experts guide the direction. SIARA supports the entire SmartView application: user experiences, business logic, integrations and configuration.
From Documentum Webtop to SmartView.
Keep the business intent.
Move the experience forward.
Where you are
Source
Documentum Webtop
Enlarge
Where you can go
Destination
OpenText D2 SmartView
Enlarge
OpenText product reference images, shown for platform context.
Customer outcomes
12 weeks for publishing.
16 weeks for pharma.
A leading publishing company moved to SmartView in 12 weeks with SIARA. A pharmaceutical company completed its move in 16 weeks. Both had originally estimated 12 months.
Original estimate12 months
Publishing with SIARA12 weeks
Pharma with SIARA16 weeks
Selected customer engagements. Delivery timelines depend on project scope and requirements.
Before you begin
A clearer path
starts here.
Is SIARA only a configuration tool?
No. SIARA is an agentic solution for building the entire SmartView application, including user experiences, business logic, workflows, integrations and the configurations that support them.
Will our team stay in control?
Yes. With Ask SIARA, your team can refine findings, ask questions about the plan and request changes. Nothing changes until you apply a proposal, and applied changes can be undone. Your team owns approval and acceptance.
Can every migration be completed in 12 weeks?
The publishing engagement took 12 weeks; the pharmaceutical engagement took 16 weeks. These are specific customer outcomes. Your migration timeline will depend on its scope, customizations, integrations and acceptance requirements. A focused discovery conversation establishes the right plan for your project.
What should we bring to a first conversation?
Bring a picture of your current Webtop application, the business processes you want to preserve and your SmartView goals. Together, we can identify a representative feature and define a useful first engagement.
Your next chapter in SmartView
Discuss your SmartView migration.
Let’s explore what SIARA can do for your migration.