Project‑Specific Document List View Properties within a Single Object Store

Background

We are currently using the IBM FileNet Salesforce Connector to manage documents across multiple business projects under the same Object Store. Today, document list view properties are configured at the Object Store level and apply uniformly to all projects using that Object Store.

IBM Support has advised that creating a new Object Store would allow separate list view configurations without impacting existing projects. However, this approach has operational and architectural constraints for our organization, as we have a limited number of Object Stores and prefer to minimize Object Store sprawl.

Current Behavior

• Document list view properties are globally applied per Object Store.
• All projects under the same Object Store see the same set of columns in the document list view.

Current List View (Project I):

• Name
• Creator
• Date Created
• Last Modifier
• Date Last Modified

Problem Statement

There is no supported way to configure different document list view properties for different projects when they share the same Object Store. This limitation forces teams to either accept unnecessary metadata visibility or create additional Object Stores, which is not always feasible or desirable.

New Requirement / Desired Behavior

Enable configuration of project‑specific (or context‑specific) document list views within the same Object Store.

Example Requirement (Project II):

• Display only:
  • Name
  • Date Created
• Hide:
  • Creator
  • Last Modifier
  • Date Last Modified

This configuration should not impact Project I or other existing projects.

Proposed Enhancement

Introduce a mechanism within the Salesforce–FileNet Connector to support multiple list view configurations under a single Object Store, for example:

• Project‑level or workspace‑level list view configuration
• Role‑based or context‑based list view settings
• Configurable mapping driven by Salesforce object, project identifier, or metadata profile

Business Value / Impact

• Improves user adoption by showing only relevant metadata per project
• Reduces confusion and information overload for new teams
• Avoids unnecessary Object Store creation and operational overhead
• Enables scalable onboarding of new projects without architectural rework

Alternatives Considered

• Creating separate Object Stores per project
  Limitation: Not scalable and constrained by current architecture and governance standards.

Priority

Medium to High
This enhancement directly impacts onboarding of new projects and future scalability of FileNet usage within Salesforce.

Ask from Product Team

1. Please confirm whether this capability exists today in any form (configuration, customization, or roadmap item).
2. If not currently available:
   • Can this be accepted as a product enhancement request?
   • What would be the recommended technical approach?
   • What are the estimated timelines for implementation and release in a future managed package version?

We are willing to formally submit and support this enhancement request as needed.

Related Support Case:TS021925533