Overview
The ACC RFI Syncer keeps Requests for Information (RFIs) synchronized between two ACC projects. When one party creates or updates an RFI, the changes automatically appear in the other party’s project. Common Use Case: A General Contractor and Architect each maintain their own ACC project. RFIs flow between them automatically.Workflow Steps
GC Creates RFI
The General Contractor creates an RFI in their ACC project with:
- Title and question
- Status set to “Open”
- Assignment information
GC Updates RFI Details (Optional)
While the RFI is still open, the GC can update the title or question. These changes sync to the Architect’s project automatically.
Architect Provides Response
The Architect reviews the RFI and provides an official response:
- Adds response text
- Attaches any supporting documents
- Changes status to “Answered”
What Gets Synced
Initial Creation
When an RFI is first created:- Title
- Question text
- Status (Open)
- Reference to source RFI ID
- Assignment to designated user in destination project
Updates While Open
The GC can update:- Title
- Question text
Official Response
When the Architect responds:- Official response text
- Response attachments (automatically downloaded and uploaded)
- Status change to “Answered”
Closure
When the GC closes:- Status change to “Closed”
Setup Requirements
GC Setup Steps
Add Kroo Service Account
Add the Kroo service account (
svcKroo@<mydomain>.com) to your ACC project as Project Admin (can view all RFIs).Confirm Coordinator Workflow
Confirm that the coordinator workflow is set for your project in your ACC tenant.
Set Start Date
Confirm the start date and time for RFI transfer (the “line in the sand”). Only RFIs created after this date will be synced.
Architect Setup Steps
Add Kroo Service Account
Add the Kroo service account (
svcKroo@<mydomain>.com) to your ACC project with all RFI permissions.Confirm Coordinator Workflow
Confirm that the coordinator workflow is set for your project in your ACC tenant.
Set Start Date
Confirm the start date and time for RFI transfer (the “line in the sand”). Only RFIs created after this date will be synced.
Start Date (“Line in the Sand”): The sync only processes RFIs created after the agreed-upon start date. This prevents syncing historical RFIs and ensures a clean starting point.
Common Issues
RFI Not Appearing in Destination
RFI Not Appearing in Destination
Possible Causes:
- Assigned user doesn’t exist in destination project
- User lacks RFI permissions
- Source RFI missing required fields (title, question, status)
- Verify user exists and has RFI access
- Ensure all required fields are filled out in source RFI
- Review Sync Details portal for error messages
Response Not Syncing Back
Response Not Syncing Back
Possible Causes:
- Attachment files too large or unsupported format
- Network issues during file transfer
- API rate limiting
- Check attachment file sizes (ACC has limits)
- Wait for next sync cycle (typically 15-30 minutes)
- Review error logs in Sync Details portal
Updates Not Reflecting
Updates Not Reflecting
Possible Causes:
- RFI not in correct state for updates
- Sync hasn’t run yet (runs every 15-30 minutes)
- Verify RFI is in “Open” state for detail updates
- Wait for next sync cycle
- Check Sync Details portal for sync timing
Getting Help
If you encounter sync issues with RFIs:- Check the Sync Details portal in the Kroo app (Two-Way Sync → Details)
- Review error messages for specific failure information
- Contact Kroo support at [email protected] with:
- Source and destination project IDs
- RFI IDs from both projects
- Error messages from Sync Details portal
- Timestamp when the issue occurred