129 results found

1. Trigger a Document Processing Configuration through Web Service (internal Document Processing, not IDP)

   We have many customers that want to use Document Processing configurations but do not want to use local folders to store the documents. Instead, they will scan it from the multifunction devices directly into the Docuware cabinet, in our case, through Ricoh Smart Integration.

   Once the document is in the cabinet, we build a workflow to call the Document Processing configuration web service. Currently this is being done with IDP, but the customer wants to use the internal Document Processing, not IDP.

   It would be great if Docuware could expose the end point of Document Processing configurations setup on the customers Docuware cloud instance. This way, we can send the Document through the workflow into Document processing, eliminating the need for a local folder.

   We have many customers that want to use Document Processing configurations but do not want to use local folders to store the documents. Instead, they will scan it from the multifunction devices directly into the Docuware cabinet, in our case, through Ricoh Smart Integration.

   Once the document is in the cabinet, we build a workflow to call the Document Processing configuration web service. Currently this is being done with IDP, but the customer wants to use the internal Document Processing, not IDP.

   It would be great if Docuware could expose the end point of Document Processing configurations setup on the… more

   9 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering feedback  ·  AdminDocuWare Product Management (Product Owner, DocuWare) responded

   Thank you for your idea. It is not part of our current plans, but we are keeping it open for the future. Votes and comments from other users help us decide what comes next, so the more interest it gets, the more likely we are to pick it up.

2. Expose user-placed stamp coordinates to Workflow / Platform API

   When a user manually places a stamp on a document, the position of that stamp can be semantically important.
   A typical example is supplier invoice processing: a user places a stamp next to a specific invoice line to associate an internal article code with that exact line.
   Currently, if a hidden stamp is used to collect a value and a workflow subsequently creates the final visible stamp through the DocuWare Platform API, the original position selected by the user cannot be retrieved or preserved.
   The workflow/API can only use predefined coordinates or automatic placement. This breaks the visual relationship between the stamp and the document content selected by the user.

   Requested enhancement
   Please expose the original manually selected stamp position to Workflow Designer / Platform API, including at least:
   - page number
   - X coordinate
   - Y coordinate
   This would allow a workflow to replace or recreate a stamp while preserving exactly the position selected by the user.
   Alternatively, provide a native mechanism allowing a workflow-generated stamp to inherit the coordinates of the triggering/user-placed stamp.

   Use case
   The user selects an article from a multi-column list such as:
   CCPC0061 - PCI Pecitape WS - Nastro impermeabile
   The resulting visible stamp should contain only:
   CCPC0061
   while remaining exactly beside the invoice line where the user originally placed it.
   This would also make the currently suggested workaround using a hidden stamp + workflow + Platform API practically usable.
   Reference: Support Request SR-297999-C5D7X

   When a user manually places a stamp on a document, the position of that stamp can be semantically important.
   A typical example is supplier invoice processing: a user places a stamp next to a specific invoice line to associate an internal article code with that exact line.
   Currently, if a hidden stamp is used to collect a value and a workflow subsequently creates the final visible stamp through the DocuWare Platform API, the original position selected by the user cannot be retrieved or preserved.
   The workflow/API can only use predefined coordinates or automatic placement. This breaks the visual relationship between… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Allow Editing of Local Data Connector Connection Details Through the UI

   According to KBA-35754, connection details cannot be edited and users must delete and recreate the connection.
   However, the Local Data Connector UI allows users to edit and save connection details. This creates confusion because the documented behavior does not match the actual UI.
   In a recent customer case, updating connection settings would have required reviewing nearly 100 workflows if the connection had to be recreated, resulting in significant administrative effort.
   Our testing showed that editing connection details directly in the LDC UI worked successfully without issues.
   We would like DocuWare to officially support editing connection details through the LDC UI and include this functionality within the supported product scope. This would reduce maintenance effort, especially in environments with many workflows, and align the documentation with the actual user experience.

   According to KBA-35754, connection details cannot be edited and users must delete and recreate the connection.
   However, the Local Data Connector UI allows users to edit and save connection details. This creates confusion because the documented behavior does not match the actual UI.
   In a recent customer case, updating connection settings would have required reviewing nearly 100 workflows if the connection had to be recreated, resulting in significant administrative effort.
   Our testing showed that editing connection details directly in the LDC UI worked successfully without issues.
   We would like DocuWare to officially support editing connection details through the LDC UI… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Expose document processing metrics for external analytics

   We store around 200k documents a year across six cabinets and management wants to see trends — how many invoices come in per week, what's the average time from receipt to approval, which departments are slowest at indexing. DocuWare's built-in views don't really do trend analysis or cross-cabinet comparisons. It'd be great to have an analytics-ready data feed or even a pre-built data mart we could query. For now we worked with a team we found when looking to hire power bi consultant and they set up an ETL job against our SQL backend, but that breaks every time DocuWare updates the schema.

   We store around 200k documents a year across six cabinets and management wants to see trends — how many invoices come in per week, what's the average time from receipt to approval, which departments are slowest at indexing. DocuWare's built-in views don't really do trend analysis or cross-cabinet comparisons. It'd be great to have an analytics-ready data feed or even a pre-built data mart we could query. For now we worked with a team we found when looking to hire power bi consultant and they set up an ETL job against our SQL backend, but that breaks every time DocuWare… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Extending the (REST) API to be able to use an Edit dialog while Updating Index values

   When storing data via the REST API, you can use a Store Dialog. With this dialog you can make sure data is being stored correctly via all the rules and selection lists etc. that are configured in the dialog. (to prohibit other values to be put in)
   What however is a massive shortcoming is if you want to update index values. In this case you are not able to use a dialog. This means an API Update Index command can send incorrect data into the system, even though you have configured all kinds of business logic in DocuWare. This means you would have to configure and maintain this logic both internally as externally in another system.

   It would be a very solid feature if we could use a parameter with this command and use an edit dialog when updating index values. This way we can make sure no incorrect data is being uploaded and business logic configured in DocuWare is being used and validated.
   Extending the (REST) API to be able to use an Edit dialog while Updating Index values

   When storing data via the REST API, you can use a Store Dialog. With this dialog you can make sure data is being stored correctly via all the rules and selection lists etc. that are configured in the dialog. (to prohibit other values to be put in)
   What however is a massive shortcoming is if you want to update index values. In this case you are not able to use a dialog. This means an API Update Index command can send incorrect data into the system, even though you have configured all kinds of business logic in DocuWare. This means… more

   6 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Custom Actions in Web Client (Toolbar & Context Menu Integration)

   Introduce the ability to define and execute custom actions directly from the DocuWare Web Client UI, both in the toolbar (right panel) and in the document context menu (right-click).

   Today, integrating external systems or custom logic (e.g. AI processing, OCR correction, data enrichment, or external workflows, whatever ) requires indirect approaches such as workflows, external links, or background automation. These solutions are powerful but not always intuitive for end users and lack a seamless user experience.

   The proposed feature would allow administrators to configure custom actions that:

   Appear as buttons in the toolbar and/or as items in the right-click context menu
   Can call external APIs (REST endpoints)
   Automatically pass document metadata (e.g. DocID, CabinetID, index fields)
   Optionally receive a response and update document index fields
   Support permission control and role-based visibility
   Provide user feedback (success, error, processing state)

   Example use cases:

   “Analyze with AI” → sends document to an AI service and writes back extracted data
   “Send to external system” → integrates with ERP/CRM or document validation services
   “Fix OCR” → triggers a custom OCR correction service
   “Export / Sync” → pushes document to external repositories

   This feature would significantly improve extensibility, reduce reliance on complex workflows for simple actions, and enable a more modern, interactive user experience aligned with current integration needs.

   This would align DocuWare with modern platforms that allow UI extensibility and would unlock many integration scenarios without requiring workaround implementations.

   Introduce the ability to define and execute custom actions directly from the DocuWare Web Client UI, both in the toolbar (right panel) and in the document context menu (right-click).

   Today, integrating external systems or custom logic (e.g. AI processing, OCR correction, data enrichment, or external workflows, whatever ) requires indirect approaches such as workflows, external links, or background automation. These solutions are powerful but not always intuitive for end users and lack a seamless user experience.

   The proposed feature would allow administrators to configure custom actions that:

   Appear as buttons in the toolbar and/or as items in the right-click context… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Support JWE as a method to encrypt URLs

   Currently, Docuware supports a rather .NET specific method for encrypting URLs. We have an application that should retrieve documents from Docuware using URL integration. This application natively supports Java Web Encryption (JWE) to encrypt (parts of) a URL. This is not compatible with the way Docuware expects URLs to be encrypted. Since JWE is a standard (RFC 7516) that is widely used by many applications, I think supporting it could be of real benefit to customers. Ideally, the encryption method should be configurable on the Docuware server.

   We had to resort to implementing a URL redirector: this takes a JWE-encrypted URL and rewrites this using the Docuware encryption algorithm and then redirects the (application-internal) browser to the Docuware URL. This introduces an unwanted dependency on a third application that we would really want to eliminate.

   Currently, Docuware supports a rather .NET specific method for encrypting URLs. We have an application that should retrieve documents from Docuware using URL integration. This application natively supports Java Web Encryption (JWE) to encrypt (parts of) a URL. This is not compatible with the way Docuware expects URLs to be encrypted. Since JWE is a standard (RFC 7516) that is widely used by many applications, I think supporting it could be of real benefit to customers. Ideally, the encryption method should be configurable on the Docuware server.

   We had to resort to implementing a URL redirector: this takes a JWE-encrypted… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Request for Product Enhancement: Enable Scheduled Refresh for DocuWare Power BI Connector

   The DocuWare Power BI Connector does not support scheduled refresh.
   We have been informed through DocuWare Support that this is due to the current product specification.
   However, scheduled refresh is essential in order to always view the most up-to-date information on Power BI dashboards. Without this capability, it is difficult to operate dashboards effectively in a production environment.
   We strongly request an enhancement to the DocuWare Power BI Connector to enable scheduled refresh. This improvement would significantly increase the usability and value of the product.

   SRNumber : SR-282397-B8X2W

   6 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering feedback  ·  AdminDocuWare Product Management (Product Owner, DocuWare) responded

   Thank you for your idea.

   Currently DocuWare is not able to create a connector for Microsoft Power BI supporting scheduled refresh.

   Microsoft only allows "Certified Connectors" for their Power BI Service. The hurdles for getting certified were not reachable in the past for DocuWare.

   It looks like Microsoft has shifted to a different path and does not certify anymore existing connectors. You can read more here: https://powerbi.microsoft.com/en-us/blog/empowering-our-customers-to-shape-the-future-of-data-connectivity-in-power-bi-and-microsoft-fabric/

9. Vorschau externer Daten in Autoindexer & Workflows

   Im Autoindex kann man unter "Datenquelle konfigurieren" eine spezifische Tabelle auswählen.
   Dort erhält man bereits eine Vorschau der Datenquelle.

   Wenn man jedoch bspw. verschiedene Tabellen miteinander joinen möchte, ist man gezwungen das über den SQL Part zu gehen.

   Dort hat man zwar die Möglichkeit die Syntax der Query validieren zu lassen (existieren Felder XY in Tabelle Z), jedoch ist dort kein Preview vorhanden um die möglicherweise komplexe Verknüpfung mehrerer Tabellen datentechnisch ebenfalls validieren zu können.

   Ebenso gibt es in den Workflows ebenfalls die Möglichkeit, bei Datenverbindungen diverse SQL Where clauses einzutragen.
   Dort hat man im Gegensatz zum AutoIndex jedoch keine Möglichkeit von Joins, geschweige denn dass es dort ein Preview der Query gibt.

   Gerade im Bezug auf die verschiedenen Integrationsmöglichkeiten sollten die Abfrage-Möglichkeiten offen und konsistent sein.

   Im Autoindex kann man unter "Datenquelle konfigurieren" eine spezifische Tabelle auswählen.
   Dort erhält man bereits eine Vorschau der Datenquelle.

   Wenn man jedoch bspw. verschiedene Tabellen miteinander joinen möchte, ist man gezwungen das über den SQL Part zu gehen.

   Dort hat man zwar die Möglichkeit die Syntax der Query validieren zu lassen (existieren Felder XY in Tabelle Z), jedoch ist dort kein Preview vorhanden um die möglicherweise komplexe Verknüpfung mehrerer Tabellen datentechnisch ebenfalls validieren zu können.

   Ebenso gibt es in den Workflows ebenfalls die Möglichkeit, bei Datenverbindungen diverse SQL Where clauses einzutragen.
   Dort hat man im Gegensatz zum AutoIndex jedoch keine… more

   •  

   •  

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Add Clip/Unclip/Staple/Unstaple endpoints to Power Automate connector

    Power Automate is great to handle multiple documents at a time (e.g. list all files in a tray & do something with them) ; it is missing some existing endpoints such as clip / unclip / staple / unstaple

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. URL Integration to open DocuWare Viewer with index dialog

    The client needs a URL integration that opens the document in the DocuWare Viewer and also displays its metadata (Index dialog) in a new window. This functionality exists today, but it is configured per user in their preferences rather than as a setting within the viewer itself.

    •  

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. webhook creation of link to collect a feedback from a webservice and trigger index and workflows

    We need to be able to create a link to give it to a webservice which will call that link to sent information like a status for paiement or an electronic signature.
    When this link is called by external services we need to exploit the content to trigger a workflow or update an index the same way it is already possible for a webservice synchronous response

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Abitlity to use Response Header fields in Web Service activity within Workflow Designer

    Hi,
    Some external APIs returns data in the header of the response. It would be very practical to be able to access those data when attributing response to data in the Web Service activity of Workflow Designer.
    Best,
    Olivier

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Fix ODBC behaviour to use default schema for user instead of user schema

    The current behaviour of ODBC Local Data Connector is not standard : when a user connects to an ODBC source, it can only currently access the schema with same name as user. ODBC standard is the default set of tables it should have access is defined as the default schema.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Add the ability to use a user's email to retrieve the associated UserName and/or UserID via a GET API call in Workflow Designer.

    Often the email address is the only data we have for a user. In order to route workflow to the user, we need to be able to do a JSON lookup of the user from the email address. At this time it is not possible.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Local Data Connector file checksum

    Local Data Connector file checksum. It's for security reason, if customer wants to add checksum to some security app.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Add ability to set custom Headers to a Web Service OAuth2 configuration

    Connecting to a D365 instance via OAuth2 requires a Custom Header to be set when obtaining the Token. This is not currently possible via the DW Web Service configuration page, there is no option for it. I am hoping for an option to define a custom header like this will become possible so that Docuware can connect directly to D365 environments.

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. API call to start a workflow

    We should be able to trigger workflows via API with a trigger reserved for API calls. The WF would return its instance ID at the end of the call.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Add Natif.ai connectors on Microsoft Power Automate

    DocuWare IDP has limited functionality. By using an iPaaS tool, we can provide a solution that maximizes the potential of Natif.ai.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Docuware on-premise support for Make.com OAuth2 and Single Sign-on

    Support for On-Premise Docuware connecting with Make.com using OAuth2 with Single Sign-on is enabled. This is a critical need

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering feedback  ·  AdminDocuWare Product Management (Product Owner, DocuWare) responded

    Thank you for your idea.

    Right now we are focusing on other topics, so we are not considering this idea for future releases. If the demand for this topic increases, we might add it to future plans.