MuleSoft - Release Notes

Core Features

• OAuth 2.0 Authentication: Secure connection to Procore API using OAuth 2.0 authorization code flow with automatic token refresh.
• Project Management Operations: Complete support for creating and updating construction projects.
• Company-Specific Context: All operations support company-specific contexts through Procore Company ID headers.
• Advanced Error Handling: Robust error handling with detailed logging and proper exception management.

Operations

System Requirements

Dependencies

Configuration Parameters

Maven Dependency

<dependency>
 <groupId>com.procore.integrations</groupId>
 <artifactId>procore</artifactId>
 <version>1.0.0</version>
 <classifier>mule-plugin</classifier>
</dependency>

Configuration Example

<procore:config name="Procore_Config">
 <procore:connection>
 <procore:oauth-authorization-code
 consumerKey="${oauth.client.id}"
 consumerSecret="${oauth.client.secret}"/>
 <procore:oauth-callback-config
 listenerConfig="HTTP_Listener_config"
 callbackPath="/mule/callback"
 authorizePath="/authorize-procore"
 externalCallbackUrl="http://localhost:8081/mule/callback" />
 </procore:connection>
</procore:config>

Create Project Example

<procore:create-project
 config-ref="Procore_Config"
 companyId="#[payload.company_id]"
 name="#[payload.name]"
 address="#[payload.address]"
 city="#[payload.city]"
 stateCode="#[payload.state_code]"
 countryCode="#[payload.country_code]"
 zip="#[payload.zip]"
 description="#[payload.description]"
 startDate="#[payload.start_date]"
 completionDate="#[payload.completion_date]"
 totalValue="#[payload.total_value]"
 enableCopyOfStandardCostCodes="#[payload.enable_copy_of_standard_cost_codes]"/>

Update Project Example

<procore:update-project
 config-ref="Procore_Config"
 companyId="#[payload.company_id]"
 projectId="#[payload.project_id]"
 name="#[payload.name]"
 address="#[payload.address]"
 city="#[payload.city]"
 description="#[payload.description]"
 totalValue="#[payload.total_value]"
 county="#[payload.county]"
 fax="#[payload.fax]"
 standardCostCodeListId="#[payload.standard_cost_code_list_id]"/>

Error Types

• Authentication Errors: OAuth token validation and refresh failures.
• API Errors: Procore API response errors with detailed error messages.
• Validation Errors: Parameter validation and business rule violations.
• Connection Errors: Network connectivity and timeout issues.
• Unexpected Errors: General exception handling with contextual information.

Unit Tests

• Comprehensive unit test coverage for all operations.
• Mock-based testing for external dependencies.
• Parameter validation testing.
• Error handling scenario testing.

Integration Tests

• End-to-end testing with Procore API. 
• OAuth flow testing.
• Real project creation and update scenarios.
• Performance and load testing.

Test Coverage

• Code Coverage: Minimum 80% instruction coverage.
• Test Scenarios: Create and update project operations.
• Error Scenarios: Authentication, validation, and API errors.
• Edge Cases: Optional parameters, null values, boundary conditions.

Available Documentation

• README.md: Quick start guide and feature overview.
• API Documentation: Detailed operation documentation.
• Configuration Guide: Connection and parameter configuration.
• Examples: Sample implementations and use cases.
• Error Handling: Error types and troubleshooting guide.

Additional Resources

• Demo Project: Complete working example in demo/ directory.
• Test Suite: Comprehensive test examples in src/test/.
• Configuration Templates: Pre-configured templates for common scenarios.

Current Limitations

• Single Company Context: Operations require an explicit company ID parameter.
• Project Operations Only: Limited to project creation and updates.
• Synchronous Operations: All operations are synchronous.
• Batch Operations: No support for batch project operations.

Known Issues

• None reported in this release.

From Previous Versions

• This is the initial release (1.0.0).
• No migration required from previous versions.

Support Information

• Maintainer: Team Strategic Integrations.
• Issue Tracking: ESI (Enterprise Strategic Integrations).
• Documentation: Available in the project repository.
• Community: Procore Enterprise Slack channel.

Maintenance Schedule

• Security Updates: As needed for critical vulnerabilities.
• Feature Updates: Quarterly release cycle.
• Bug Fixes: Monthly patch releases.
• Documentation Updates: Continuous improvement.

Version 1.0.0 (Current Release)

• Initial Release: First public release of Procore Connector.
• OAuth 2.0 Authentication: Secure authentication with Procore API.
• Create Project Operation: Complete project creation functionality.
• Update Project Operation: Full project update capabilities.
• Comprehensive Error Handling: Robust error management and logging.
• Company-Specific Operations: Support for multi-company environments.
• Advanced Project Features: Support for all major project parameters.
• Documentation and Examples: Complete documentation and demo project.
• Test Coverage: Comprehensive unit and integration tests.

Development Guidelines

• Follow MuleSoft development best practices.
• Maintain 80% minimum code coverage.
• Include comprehensive error handling.
• Provide detailed documentation for new features.
• Follow established naming conventions and code structure.

Testing Requirements

• Unit tests for all new operations.
• Integration tests for API interactions.
• Error scenario testing.
• Performance testing for new features.