If the image needed is in the CIP cloud storage, the user can request for it to be retrieved and brought back into STAC.

When the case is deleted from STAC using the Delete wizard, the images are also deleted from the CIP cloud storage.
The system sends a request to have the images deleted from the storage, but there is a built-in safety net of 10 days after the request is sent to mitigate a mistake or other such scenario.
The files that are set for deletion are not easily accessible to the user. However, the circuit can contact CIP and someone from our team can go in and manually cancel the deletion process and make it available again in STAC.

No, once the file(s) is requested to be deleted from storage the file will no longer be available in STAC.
However, STAC does keep the file in storage for the 10-day grace period before actually performing the deletion of the file from the cloud storage.
Yes, the file(s) and cases that are set for deletion will be deleted from the cloud and will not need to be brought back into STAC first to be deleted.
Text messages and phone calls can easily be translated to other languages as part of the basic CIP Portal services.
The translation services are super handy especially with the large population in Florida that speaks Spanish, Portuguese, and Creole.
STAC can translate to a few languages currently, including:
A message comes back from the CIP PORTAL and is added to the Image log when a recipient adds a new collaborator.
The comment field displays the email of the collaborator that got added.

All collaborators will have full access to ALL the user's files. The user is warned about this while they are adding a new collaborator.When the message was sent but the response from the provider is still pending:
The status field will be -> SENT, while the Delivered field will be -> Pending.
When the message was successfully delivered:
The status field will be updated to -> DELIVERED, and the delivered field will read -> text/voice message delivered.
When the message was not successfully delivered:
Then the status field will be updated to -> UNDELIVERED, delivered field will be -> text/voice message delivered, and the error message field will show the error message from the provider’s platform.
a. The link was sent to an incorrect email address
b. The email may be in Junk or Spam folders
c. Discovery is still uploading to the Portal
Confirm the correct spelling of the email address
Check Junk or Spam folders. Also, users are not required to go through the link in the email, if they have documents pending, they can still log into the CIP Portal at https://portal.cipi.net/ with the account credentials related to the address with which the discovery was shared and access all of their files.
If files are still uploading to the portal, wait and check back later. Large files can take hours to complete the upload process to the CIP Portal. Files over 5 gigabytes (5 GB) upload overnight.

Please log in into the CIP Portal and double check the file is there. Users may have not received an email notifying about the new file. If users see the file but didn’t receive an email, they can change their email preferences to be notified about every single one.
a. Large file downloads may be abruptly interrupted with a “Network error” message. Internet Browsers are not able to handle the download of such large files properly. Users can easily resume any interrupted download by:
b. the workstation/computer may not have enough available disk space
A1. Manually resuming the interrupted download
A2. Using a download manager
B. The CIP Portal displays the size of the file the user is trying to download. Check the available space on the drive location where the user will be saving the file. If the number is less than the size of the download, then the workstation/computer will not download the file.
If a circuit is sending a mass text, there is not an easy way to see if all the messages were sent or received.
CIP recommends the user to always ask for a reply, that way it is certain that communication was made. The users in STAC can also check the CIP Portal Status Search in the Search menu to check the status of the messages.
Users can share any file that is added or linked to STAC. However, those must be files stored on the circuit’s servers, not on an external cloud storage.
Recipients can add their own collaborators to receive files on their behalf, and STAC will track who downloaded the file and will display the name of the person that downloaded the file on the Image Log.
There are FDLE requirements we must follow in order to keep everyone’s servers secure. So, external parties can send a circuit files, but the circuit will first need to send them an authorization.
Video transcription and other services related to videos are only available with the CIP storage services.
A single SMS message technically supports up to 160 characters. If a text has more than 160 characters, the text will be split into multiple messages (segments) to accommodate for larger messages.
However, for SMS messaging, it is recommended to send messages that are no more than 160 characters to ensure the best deliverability and user experience.
In the attached document was a link that goes to a Police Departments evidence program, when the document is uploaded into STAC the link no longer works we get an error.
Wrong Link
You have clicked on an invalid link- Please make sure that you have typed the link correctly- If are copying this link from a mail reader please ensure that you have copied all the lines in the link.

This is an issue with the recipient. They may have a system in place that modifies the link embedded in the email.
To troubleshoot and make sure it is not a problem with the link itself, the user can always share a copy of this file with themselves and try to download it.

The error above indicates the token CIP uses to send data has expired. The file must have taken too long.
There are a couple things we can try to handle the larger files before the token expires.
The first thing that can be done is increase the “Upload block size in MB” and/or the “Upload timeout (in minutes)” in the file share section in the configurations.
a. The recipient has not yet created a CIP Portal account
b. The account credentials the recipient is using does not match the email address to which they were shared
Create a free CIP Portal account
Confirm the email address to which the discovery was shared is the same email address in the CIP Portal account
Files are shared for a maximum of thirty (30) days. After 30 days have passed, the files are deleted.
Contact the circuit regarding the related case to reshare the files through the Portal. (Note: Discovery shared that is still within the 30-day window as described above cannot be reshared to the same recipient’s email address again in the same timeframe.)
When uploading files to the portal there may be an error that does not let the user send a specific file. If the error message reads "The transfer failed", it is most likely due to the connection between the webserver and the storage server getting lost while the system is attempting to upload this file. STAC then has to restart the upload.
In order to verify the problem is with the connection, copy the file to the webserver attached to the case and try to send it.
a. The files are in a “zipped” format
b. The correct viewer/player is not installed on the workstation/computer
a. Unzip/extract the files from the zip folder. Ensure the workstation is using the correct player. (Users can conduct a brief internet search on the file extension to find a player to view the file)
The CIPPortalUpload job will upload the actual files such as media, that are sent through the Portal.
The CIPPortal job handles sending things like text messages, forms, and also getting back some information from the portal such as logs on items that were previously sent.
STAC will automatically cancel the ZIP file process if:
Users will know that the ZIP Process was cancelled because they will receive an error message.
If an Agency sees the error below on the SQL jobs:
ERROR: Unexpected error in p_exec_webservice: EXEC sp_OAMethod 16711422, ‘send’ [SQLSTATE 42000] (Error 50000) > > > > > ERROR: Unexpected error in p_exec_webservice using @url=
One of the possible solutions is to be sure the OLE automation is enabled by running the following SQL command:
EXEC master..sp_configure 'show advanced options', 1
RECONFIGURE;
EXEC master..sp_configure 'Ole Automation Procedures', 1;
RECONFIGURE;
In the Directory, users have the ability to mark an address as confidential. If the address is marked as confidential it will NOT be printed on documents or exported.

They need to make sure that they do NOT have anything in the Event to Share Images field in the Image Options code table. If that field is left blank, then STAC will automatically send Discovery once it is flagged.
For this situation: Files can be flagged as discovery, but they are only sent after a specific Event is added to the case, then triggering all pending Discovery in the case to be sent. If new Discovery is flagged after the special Event was added, then the new discovery will not be sent until the Special Event is added to the case again.
So, when the event to send Discovery is added to a case for the second or third time, STAC is going to send the records that are flagged as Discovery but have NOT yet been sent.
The important setup that differentiates the type of document being created is on the E-File tab of the Document maintenance screen.
The admin will need to fill out the information in the E-service section.
Even E-service documents require the Administrator to add the E-file relationship because that is the relationship that will approve the document.There are multiple types of documents and users often have trouble locating their documents.
Once a document is merged it will automatically be added to the document tab, even while it is still pending approval. If there was an image type/sub-type set in the document configuration it will only display on the image tab after the document was approved. However, e-file and e-service documents have a few more conditions that need to be met before the document is saved in the image tab.
If a document is in the pending review and it gets rejected; the document will be removed from the case.All documents will be saved in the document tab. The only other place that e-file and e-service documents will be saved is in the image tab. E-file and E-service documents will only be saved in the image tab if it satisfies 3 conditions:
Only after all 3 of the above conditions are met, will the e-file and/or e-service document be saved in the image tab of the associated case.
All documents will be saved in the document tab. E-documents will be saved in the document tab and in the image tab if the image type/sub-type are filled out on the information screen.
The e-document will only be added to the image tab if the image type/sub-type is filled out in the Information screen and after the document gets approved.
Many circuits end up accumulating a number of documents because users are always asking for a new document. As system administrators, it is difficult to keep track of all the documents. The queries below will show some document related data.
This first query shows users how many times active documents have been merged since 1/1/2025. Administrators can easily adjust the date for a longer/shorter timeframe.
--Documents merged since ---This second query displays all active documents that have not been merged since 1/1/2025.
These queries can be used to identify documents that could be inactivated. Keep in mind, having unused documents can not only take more of the system administrators time, but it also take time from users when they have to decide between the numerous different templates.
The query below displays duplicated document records that point to the same template. This can be very problematic because a change in one of these records can break the merge when users try to merge using one of the other records. In STAC, the same document can be displayed under multiple categories.
-- duplicated documents by template
All the merged documents will be saved in the Document tab.
If the image type/sub-type is filled out for the e-document and email on the information screen, it will also appear on the image tab, but it will only appear after the Document was approved.
Efile and Eservice Documents will NOT be deleted/removed from the Document tab, even if the associated Document Event or associated Subpoena/Deposition gets deleted from the case.



Criteria:
When a document is e-filed in STAC, we first receive a Portal filing Id, this means that FACC has received the filing. Then, STAC will wait for a filing response from FACC.
Sometimes, after already receiving all of the information above users will get an error stating “FACC Status error: Document cannot be e-filed”
This means that there was an issue with FACC trying to repackage this information to send it to the Clerk.
To troubleshoot this error, we recommend the circuits to contact FACC. When contacting FACC, they will inquire for the Portal Filing ID number of the case in question and they will be able to further assist the user in understanding why they could not E-file the document(s).
If the user attempts to call the Clerks office with this error, they will not be able to assist the user because they have not received the filing yet, it is still being processed by FACC at the time of the error.
1- There are scheduled jobs that run on the server that handle processes like email, e-file, exchanges, etc. Be sure these jobs are enabled.
2- Under Setup > Configuration > Exchanges, there are entries for the Regular E-file and E-file or Proposed Orders. Be sure both of these exchanges are active, and that there is a valid username and password.
| Address | Function |
|---|---|
| https://test.myflcourtaccess.com/ | FACC portal. Agencies can test their credential here |
| https://test.myflcourtaccess.com/BulkFilingReview/proxy.svc | Address for bulk E-file. |
| https://test.myflcourtaccess.com/ProposedOrders/MTOMProxy.svc | Address bulk E-file Proposed |
| Address | Function |
|---|---|
| https://myflcourtaccess.com/ | Production site for the FACC portal. Users can test their credential here |
| https://myflcourtaccess.com/BulkFilingReview/proxy.svc | Address for bulk E-file. |
| https://myflcourtaccess.com/ProposedOrders/MTOMProxy.svc | Address for bulk E-file Proposed Orders |
The main reason for this problem is because the BAR number for the attorney in STAC does not match what FACC has on its database. Unfortunately, leading zeros in the BAR number do make a difference.
When this problem happens, you will see the filing at the FACC portal using your agency’s name as the filer.
STAC sends the Judge’s Bar Number to FACC which sends the document to the email they have on file.
If a judge is receiving proposed orders on the wrong email, most likely they have 2 different accounts on the FACC portal with the same bar number. Please contact FACC so they can fix the Judge’s accounts.
This issue is typically something that happens on the FACC side.

There are 4 email fields available when creating a Directory. They have the Email, CC_email, Email_alternative_eservice, and Email Subpoena.
The Email_alternative_eservice is ONLY used for E-service documents. If there is NOT an email defined in this field, then STAC will use the Email and CC_email field to eservice the recipient.
The Email_Subpoena is ONLY used for documents that have the Create Subpoena Record field checked in the document configurations. If there is NOT an email defined in this field, then STACweb will use the Email and CC_email field to email the Subpoena.
All of the other emails generated for the Directories will be sent to both the email and cc_email
When the email stops working, finding the cause of the problem can be a complicated process.
The easiest way to test and see an error message is to use the “Test email” button from the Email Options screen. This process calls the email server immediately and returns any error message from the email server.
Since these problems can be caused from a number of places (smtp server, network, firewall, etc), we can use a VBS script to test the email outside BOMS or STAC. In fact, this script can be executed from any server and workstation, and it should help the user identify which component is causing problems.
When testing this script, first the user must be sure they are sending an email. That means running the script from the webserver or from another server or workstation.
Keep in mind there are number of settings related to the SMTP server, including user name and password, or having your webserver whitelisted, or no validation at all.
The script below should be saved as a vbs file. You can change the parameters to match the credentials of your server and to test alternate settings like different ports, etc.

Set emailObj = CreateObject("CDO.Message")
emailObj.From = "your email address"
emailObj.To = "recipient"
emailObj.Subject = "Test"
emailObj.TextBody = "Test 6/30/22 10:20"
Set emailConfig = emailObj.Configuration
emailConfig.Fields("http://schemas.microsoft.com/cdo/configuration/smtpserver") = "your smtp server"
emailConfig.Fields("http://schemas.microsoft.com/cdo/configuration/smtpserverport") = 25
emailConfig.Fields("http://schemas.microsoft.com/cdo/configuration/sendusing") = 2
emailConfig.Fields("http://schemas.microsoft.com/cdo/configuration/smtpauthenticate") = 1
emailConfig.Fields("http://schemas.microsoft.com/cdo/configuration/smtpusessl") = false
emailConfig.Fields("http://schemas.microsoft.com/cdo/configuration/sendusername") = "your email address"
emailConfig.Fields("http://schemas.microsoft.com/cdo/configuration/sendpassword") = "Password1"
emailConfig.Fields.Update
emailObj.Send
If err.number = 0 then Msgbox "Done"
The Event type will need the Message type to be set to Email and select an email template that should be sent to a relationship in the case when the event is added. After that Event type is saved, select the Event type that is going to send the emails > Options > Event type email relationships. That is where the administrators can select the relationship that will receive the email when the event is added.
To troubleshoot this problem the user can use the Outbox Search option under Searches to see if the emails were generated and not sent or if they are not there at all. Additionally, the administrator can check if the jobs in the SQL server are enabled and running.
When configuring the emails to use Gmail using Googles API, and the following error appears: “Error sending message; The system cannot find the files specified.”
Go to IIS > The application pool that is serving the application > Advanced Properties > Load User Profile. Please make sure it’s set to true. (this will reset the application and disconnect all users)
If Load User Profile is already set to true, change the user associated with the STAC/BOMS App pool to an admin account.

Administrators are able to configure emails and email templates to be sent from the Agency email or the user created email. When the configurations in Email Options or Email/message Template is configured to send from or send as the User created. The administrator must make sure that the users account is authenticated to allow them to send the email.
Error sending message; Error sending email via smtp. Transaction failed. The server response was: 5.2.252 SendAsDenied; [AgencyEmail@net.com] not allowed to send as [UsersEmail@net.com]
The administrator must give the user Delegate access in order for STAC to send these emails using the User created email
Since defendants representing themselves is an exception, a lot of agencies don’t have them automated, and they just send them copies of documents using the email function on the Image tab.
One solution would be to create a relationship for PROSE and add the defendant to that role in addition to the DEF record. This allows using the mechanisms in place to automatically e-service these relationships.
If one record is selected, then the comment will appear in the comment field and the user will be able to edit or add any new information to the comment.
However, if the multi-select is enabled and there are multiple records selected. Then, STAC will populate a blank comment field and the new comment will Overwrite any previous comment.

To contact FDLE for any questions, please call FDLE anytime from 8am-5pm eastern standard time (850)410-7140
FDLE has a FCIC number for ordinances. Municipal:7500, County:8500As a prosecuting agency, we occasionally receive cases from non-arresting agencies such as the Department of Children & Families or Department of Financial Services. If our agency decides this is a prosecutable case, we Direct File an Information and the Clerk issues a Capias for the Defendant. Since this case was not initiated with an arrest, is an Arresting Agency required? If so, would the State Attorney’s Office be that agency, via the Information, so that we would use our ORI or would the agency that served the Capias be the correct agency to use?
In this situation it is advised to use your agency as the arresting agency ORI
This error is most likely caused by 3 reasons:

[FDLE data transparency annual report submission Token Error: Not Found]
To fix the error:

[FDLE data transparency annual report submission Token Error: Unauthorized]
This error message is most likely caused by 2 problems:
“Case report submission Error: [ERR_FLPRT_00402-At least one name for an arrestee or case subject must be provided with the Name Category of “provided” to indicate the name used at the time of arrest or case initiation.]"

[No FDLE charge level code specified for statute 782.04(1)(a)1. It is required when sending statute Chapter/Section]
To fix the data and resubmit the FDLE report:

If one of the charges have a FDLE level = *, The user should edit the charge and add the appropriate charge level to fix the error message.[Dispo action WD has no fdle code.]
To fix the data and resubmit the FDLE report:
[No FDLE Charge Degree code specified for Statute (Statute No).] -
To fix the data and resubmit the FDLE report:

[No FDLE Number nor Chapter defined for Statute (Statute No).]
To fix the data and resubmit the FDLE report:
[No section defined for statute {charge.StatuteNumber}. It is required when sending statute Chapter/Section.]
To fix the data and resubmit the FDLE report:
[Ethnicity FDLE code not provided for HISPANIC]
To fix the data and resubmit the FDLE report:
If users are still receiving the FDLE Ethnicity error but the Ethnicities are matched to their appropriate FDLE codes. Then, the Administrator will need to add the Unknown FDLE code to the Not Defined Ethnicity as we see in the screenshot below.
[Drug name Heroin has no fdle code.]
To fix the data and resubmit the FDLE report:
The CJDT FDLE IEPD Certification Requirements:
CJDT Testing Guidelines Summary for the CJJIS Council presentation:
Prerequisite: The agency must be able to generate XML files per the specifications and successfully establish the connection with CJIS Portal.
FDLE will verify that elements successfully populate the CJDT database and that transactions aren’t being dropped before opening access to Production.


To fix the data and resubmit the FDLE report:
The data sent to FDLE does not get removed or recalled once a case is deleted in STAC.
In this situation, the user should delete the submission first, and then delete the case from STAC
The field is called “Group Name for imported image records”, and it is a free text field for the use to add the Name of the group for these images. When this configuration is set, the system will add imported images from the exchange to a group. The system will append the date the images are imported to the group name. The image types that will be added to a group must also be configured in the Event Type code table
Users also have the ability to group documents after they are merged, to be saved in one group in the Image tab. This configuration is set in the Document Maintenance under the Information tab; there is a field called “Image Group Name” which is where the user can add the name of the group.
Users need to configure the document to get saved in the image tab.
This is done by: Setup > Document Maintenance (Fill in the Image Type fields on the bottom of the screen)
STAC has a feature called the image purge, it can be configured to the circuit's needs in the image Options code table. The purge will validate the last deposition date and age of the image to be deleted.

If an administrator received the error below while upgrading STAC on a new IIS server.

The administrator trying to upgrade will need to grant rights to the user they are logged in as.
For example, if it is an administrator or a personal account, the account must have full rights to the IIS folder, in order to run an upgrade.
Ctrl+Click – Select individual items (checkboxes appear).
Shift+Click – Select a range.
Click (without Ctrl) – Clears selection.
Users can preview selected cases by clicking inside the list.

All records deleted are saved in the log tables.
For the requests it is the lb_requests table where the administrator should look for z_action_type= ‘D’
If it still didn’t work using Chrome or Edge browsers:
Then, we suggest the Administrator to go to IIS server C:\windows\temp and delete any file that has the extension .tmp This might be because the circuit is running out of space, and those are temporary files that were created when a user opens a crystal report.
If it still didn’t work
We also suggest:
If someone is editing a SQL statement from a report directly inside STAC and they mess it up or alter the SQL syntax, the STAC Administrator can recover the original SQL Syntax from SQL.
The administrator can recover a reports original SQL Syntax by checking the ld_report table in SQL.
If reports were working at one point during the day and they suddenly stop working or are appearing blank, the STAC Administrator will be receiving a lot of emails from their users.
The Administrator will need to clean up the c:\windows\temp folder.
The reason this folder needs a clean up is because Crystal creates temp files whenever users run the reports like tmpXXXX.tmp and most likely it ran out of names. Once it runs out of options to name the file, it will no longer allow users to open/run reports until this folder is cleaned up.
If the administrator doesn’t want to remove everything from the temp folder, then they can just remove the tmpXXXX.tmp files.This is a huge issue because it invalidates all backups scheduled by CIP. Since CIP’s backups are created with the premise that we have the FULL backup created around 1am, and all of the transaction log is appended to the same backup. When an external backup is performed, CIP’s transaction logs become worthless because the full backup is outdated.

Additionally, many of these 3rd party backup tools, will run multiple full backups if they perceive other backups were executed. This will cause the server to work in overload with multiple full backups being executed throughout the day and cause slowness.
This happens when the backup software is copying the backup file created using SQL and SQL attempts to append another transaction log to that file. Since the step that appends the transaction log to the backup file is recurrent, this error is usually not serious. This is because the whole transaction log will be stored the next time the job runs, and the file is accessible.
This is only a problem when the process of backing up the backup files takes several minutes or even a few hours.
A common problem is not deleting the backups created by the upgrade process.
The upgrade application creates a full backup of the database before any update is applied. CIP purposely does NOT delete the backup file at the end of the upgrade, to guarantee there is a copy available regardless of any problems. These backups created by the upgrade application are stored in the same folder the regular backups are created, but they are named using the name of the database and the date and time the upgrade was executed.
Once the upgrade is finished, these files can be deleted, but it is good practice to at least keep the most recent file.
We recommend deleting all older files before upgrading. Keeping these files will fill the disk and make the regular backups take longer for more files have to be copied.
Each job is set to run on a specified schedule, but sometimes the job doesn’t actually run in the interval that is set in SQL.
As far as the interval, the jobs start at the designated time as long as they are not already running.
For example, if a job that is schedule to run every 2 minutes runs for 3 minutes, the next run won’t start until the previous run is completed. Which will mean that the job is not running every 2 minutes, but it is running every 2 minutes from when the last job has been completed.
Jobs may fail from time to time, but if every run fails, please contact CIP.
Please note: These are general tutorial and setup guides to help offices automate certain process in STAC. There may be specific processes or business rules unique to each office that could require updates or adjustments to this configuration.
This guide will help an agency setup Request forms through the CIP Portal and trigger image review notifications when documents are submitted.


Go to: Configuration > Relationship Trigger > Add Learn how to create a relationship trigger
Input Parameters: Select a relationship type (e.g., “Agency”) that will trigger the addition of another relationship.
Output Parameters: Define the relationship that will receive the form (e.g., “Records”).
Go to: Configuration > Relationship Trigger > Add
Input Parameters: Relationship type, location, or case type filters as needed.
Output Parameters: Select the Request form created in Step 1.
Go to: Configuration > Image Trigger > Add Learn how to create an Image trigger
Input Parameters: Image type, case filters, and action (Image Added).
Output Parameters:
Category: Image Review
Action to Trigger: Image Review
Relationship Type to Notify: Select who should review uploaded images