4 results found

1. Space console zoom issues on load - missing frame, squished elements

   I am seeing issues with the Floors frame not appearing when space console is loaded (OOTB), but it will appear once you adjust browser zoom (plus or minus). See the difference in the attached screenshots. This has occured in multiple environments and for multiple users. Also, when resizing the window the elements of the page do end up being squished together though this is not Space Console specific.

   •  

   •  

   5 votes

   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  ·  Space  ·  Delete…  ·  Admin →
   Closed  ·  ying.qin@SpaceIQ.com responded

   I am closing this idea as a bug – please contact CS for this issue

2. Support for Metric Drawings

   Introduce support for Archibus to display and export floor plans drawn with metric measurements

   2 votes

   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  ·  Space  ·  Delete…  ·  Admin →
   Closed  ·  ying.qin@SpaceIQ.com responded

   Hi.

   I am closing this idea as a bug since we have an existing JIRA to track this issue.

   Thank you!
   Ying

3. Integrate Uservoice forum with Archibus
   2 votes

   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

   Closed  ·  0 comments  ·  Platform  ·  Delete…  ·  Admin →

4. Error in log file related to document storage corrupted for field_name of Building Photo

   I raised this issue with the Archibus Tech Support team and they advised me to submit this issue on “UserVoice”:

   It appears that if there is no building_photo stored in the bl table, an error is logged each time a user logs in.

   Line 74256: The document storage is corrupted for document field=[{tablename=bl, fieldname=bldgphoto, pkeyValues={blid=123456}}]

   Can the check be disabled if there are no photos uploaded?

   A client has 808 buildings, only 2 have photos uploaded and 2 where I created a PNG to test my theory. Only 345 errors were logged which is still a lot and will affect system performance since this occurs for each user with that home page assigned.

   I was told to add this to the logging.xml file:

   <category name="com.archibus.docmanager">
   <priority value="off" />
   </category>

   Unfortunately this does not suppress the error.

   I was told: Since this check is being done by standard document management code and home page code, both of which are in the non-modifiable core, I don't believe any part of it could be co-opted or modified to suppress these warnings or stop these checks. Unfortunately, the most that could probably be done in this case is to submit a Uservoice as an improvement item.

   Please review this issue and please consider a way to resolve that can be addressed ASAP?

   Many thanks!

   I raised this issue with the Archibus Tech Support team and they advised me to submit this issue on “UserVoice”:

   It appears that if there is no building_photo stored in the bl table, an error is logged each time a user logs in.

   Line 74256: The document storage is corrupted for document field=[{tablename=bl, fieldname=bldgphoto, pkeyValues={blid=123456}}]

   Can the check be disabled if there are no photos uploaded?

   A client has 808 buildings, only 2 have photos uploaded and 2 where I created a PNG to test my theory. Only 345 errors were logged which is still a… more

   •  

   1 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  ·  Sustainability & Risk  ·  Delete…  ·  Admin →
   Closed  ·  AdminFred Kraus (Admin, Eptura) responded

   After review we agree this is not an enhancement. Closing as a bug, and redirecting to be fixed in Jira.