Lithosphere The Lithium Community

%3CLINGO-SUB%20id%3D%22lingo-sub-265363%22%20slang%3D%22en-US%22%3Efind%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-265363%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%20-%20I've%20recently%20come%20back%20to%20administering%20a%20Lithium%20community%20after%20an%20absence%20of%20a%20few%20years%2C%20so%20I'm%20excited%20about%20many%20of%20the%20changes%20and%20functionality%20now%20available.%20But%20I'll%20admit%20to%20getting%20lost%20a%20few%20times%20in%20the%20new%20layout.%20I%20was%20hoping%20others%20could%20provide%20some%20assistance%2C%20as%20we%20are%20adjusting%20our%20moderation%20procedures%20and%20were%20looking%20for%20some%20help%20on%20how%20to%20execute%20them.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESpecifically%2C%20we%20have%20launched%20a%20process%20to%20escalate%20threads%20with%20no%20reply%20to%20our%20support%20team%2C%20but%20we%20want%20to%20do%20so%20only%20in%20those%20cases%20where%20the%20issue%20can%20be%20answered%20on%20the%20community.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20rather%20than%20enable%20the%20automatic%20escalation%20setting%20in%20the%20admin%2C%20we%20turned%20on%20manual%20escalation%20so%20our%20moderation%20team%20can%20apply%20their%20judgement%20before%20generating%20the%20ticket.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20challenge%20is%20that%20we%20want%20to%20wait%2024%20hours%20after%20a%20post%26nbsp%3Bbefore%20we%20review%20for%20escalation.%20But%20for%20the%20life%20of%20me%2C%20I%20don't%20seem%20to%20find%20a%20way%20to%20query%20in%20the%20Moderation%20console%20or%20the%20Advanced%20search%20for%20posts%20without%20a%20reply%20that%20are%2024%20hours%20old%20%3CSTRONG%3Eor%20older%3C%2FSTRONG%3E.%20Lots%20of%20options%20to%20view%20by%20the%20last%20day%2C%20week%2C%20month%2C%20what%20have%20you%2C%20but%20nothing%20that%20lets%20us%20see%20things%20%3CSTRONG%3Eat%20least%3C%2FSTRONG%3E%2024%20hours%20old.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20anyone%20else%20have%20this%20use%20case%3F%20How%20have%20you%20addressed%20it%3F%20Is%20there%20maybe%20a%20way%20to%20manipulate%20the%20search%20URL%20query%20string%20parameters%20to%20get%20this%20list%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance%20for%20any%20and%20all%20help!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-287439%22%20slang%3D%22en-US%22%3ERe%3A%20find%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-287439%22%20slang%3D%22en-US%22%3E%3CP%3EWould%20this%20do%20it%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3E%26lt%3B%23assign%20user_id%20%3D%20user.id%2F%26gt%3B%0A%26lt%3B%23assign%20tz%20%3D%20restadmin(%22%2Fusers%2Flogin%2F%24%7Buser_id%7D%2Fsettings%2Fname%2Fconfig.timezone%22).value%2F%26gt%3B%0A%26lt%3B%23assign%20beforelong%20%3D%20.now%3Flong%20-%20(24%20*%2060%20*%2060%20*%201000)%2F%26gt%3B%0A%26lt%3B%23assign%20before%20%3D%20beforelong%3Fnumber_to_datetime%3Fiso(%22%24%7Btz%7D%22)%2F%26gt%3B%0A%26lt%3B%23assign%20query%20%3D%20rest(%222.0%22%2C%20%22%2Fsearch%3Fq%3D%22%20%2B%20%22SELECT%20id%2Csubject%2Cpost_time%2Cview_href%20FROM%20messages%20WHERE%20depth%20%3D%200%20AND%20replies.count(*)%20%3D%200%20AND%20conversation.last_post_time%20%26lt%3B%3D%20%24%7Bbefore%7D%20ORDER%20BY%20conversation.last_post_time%20DESC%20LIMIT%205%22%3Furl(%22UTF-8%22))%20%2F%26gt%3B%0A%26lt%3B%23list%20query.data.items%20as%20q%26gt%3B%0A%20%26lt%3Ba%20href%3D%22%24%7Bq.view_href%7D%22%26gt%3B%24%7Bq.subject%7D%26lt%3B%2Fa%26gt%3B%20-%20%24%7Bq.post_time%3Fdatetime%7D%26lt%3Bbr%2F%26gt%3B%0A%26lt%3B%2F%23list%26gt%3B%3C%2FPRE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-287425%22%20slang%3D%22en-US%22%3ERe%3A%20find%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-287425%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.lithium.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F62789%22%20target%3D%22_blank%22%3E%40sdodds%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethis%20URL%20works%20fine%20in%20our%20responsive%20%3CA%20href%3D%22https%3A%2F%2Fsbbcffffs-community.sbb.ch%2Ft5%2Fforums%2Frecentpostspage%2Fpost-type%2Fmessage%2Fpage%2F1%3Fprofile.language%3Den-gb%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3ECommunity%3C%2FA%3E%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3Ehttps%3A%2F%2Fsbbcffffs-community.sbb.ch%2Ft5%2Fforums%2Frecentpostspage%2Fpost-type%2Fmessage%2Fpage%2F1%3Fprofile.language%3Den-gb%3C%2FPRE%3E%3CP%3EI%20just%20added%20the%20language%20parameter%2C%20to%20display%20the%20english%20posts.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20just%20noticed%20that%20there%20is%20probably%20a%20small%20problem%20with%20the%20display%20of%20the%20number%20of%20replies.%26nbsp%3BI'll%20check%20that%20with%20our%20community%20agency.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20%26amp%3B%20Regards%2C%20Daniel%3C%2FP%3E%3CP%3ECommunity%20Manager%2C%20Swiss%20Federal%20Railways%20(SBB)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-287333%22%20slang%3D%22en-US%22%3ERe%3A%20find%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-287333%22%20slang%3D%22en-US%22%3E%3CP%3EHmm%20-%20we're%20not%20yet%20on%20Responsive%20in%20our%20community%2C%20so%20perhaps%20that%20is%20the%20issue%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20first%20URL%20(below)%20shouldn't%20be%20using%20any%20customizations%20I'm%20aware%20of%20-%20change%20the%20domain%20and%20it%20should%20work%20fine.%3C%2FP%3E%3CPRE%3Ehttps%3A%2F%2FOUR.COMMUNITY.DOMAIN%2Ft5%2Fforums%2Frecentpostspage%2Fpost-type%2Fmessage%2Fpage%2F1%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20else%20on%20the%20Responsive%20platform%20tried%20these%20URLs%20yet%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-287273%22%20slang%3D%22en-US%22%3ERe%3A%20find%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-287273%22%20slang%3D%22en-US%22%3EThanks%20both%20for%20that!%20Neither%20URL%20works%20for%20me%20(points%20me%20to%20the%20homepage)%20so%20I%20guess%20that's%20to%20do%20with%20the%20customization%20that%20was%20made%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-284794%22%20slang%3D%22en-US%22%3ERe%3A%20find%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-284794%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.lithium.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F62789%22%20target%3D%22_blank%22%3E%40sdodds%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20a%20lot!%26nbsp%3BI%20like%20to%20try%20it%20out.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDaniel%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-284147%22%20slang%3D%22en-US%22%3ERe%3A%20find%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-284147%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fcommunity.lithium.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F53726%22%20target%3D%22_blank%22%3E%40schwarzd%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.lithium.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F51870%22%20target%3D%22_blank%22%3E%40edgiansante%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20the%20problem%20with%20my%20example%20was%20the%20%22%26amp%3Bsearch_page_size%3D100%22%20parameter.%20I've%20found%20this%20parameter%20doesn't%20like%20amounts%20over%2050%20for%20some%20reason.%20Try%26nbsp%3B%3CSPAN%3E%22%26amp%3Bsearch_page_size%3D50%22%20or%20lower%2C%20instead.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAnother%20issue%20I%20found%20is%20that%20pagination%20controls%20on%20the%20page%20break%20the%20filter%20I've%20set%20via%20manual%20query%20string%20parameters.%20So%20we%20no%20longer%20use%20them%20with%20the%20modified%20URLs%2C%20we%20use%20the%20parameter%20%26nbsp%3B%22%26amp%3Bpage%3D1%22%20and%20adjust%20it%20in%20the%20URL%20to%20go%20from%20page%20to%20page%3A%20%22%26amp%3Bpage%3D2%22%2C%20%22%26amp%3Bpage%3D3%22%2C%20etc.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20also%20checked%2C%20and%20both%20%22%2Fbizapps%2Fpage%22%20and%20%22%2Fbizapps%2Fbizappspage%22%20work%20in%20my%20community.%20So%20for%20compatibility%20it%20is%20probably%26nbsp%3Bbest%20to%20stick%20with%20the%20latter.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFinally%2C%20since%20I%20posted%20this%20message%20originally%20we%20have%20standardized%20on%20three%26nbsp%3BURLs%20we%20use%20in%20our%20moderation%20process%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1)%20For%20our%20moderator%20initial%20review%20of%20every%20message%3A%3C%2FP%3E%3CPRE%3Ehttps%3A%2F%2FOUR.COMMUNITY.DOMAIN%2Ft5%2Fforums%2Frecentpostspage%2Fpost-type%2Fmessage%2Fpage%2F1%3C%2FPRE%3E%3CP%3EStraightforward%20view%20of%20every%20post%20(forum%20topic%20and%20replies%2C%20blog%20articles%20and%20comments%2C%20etc.)%2C%20though%20we%20also%20filter%20by%20category%20for%20some%20moderators%20who%20focus%20on%20specific%20areas%20using%20%22%2Fcategory-id%2FOURCATEGORYID%2F%22%20e.g.%20%22%2Fcategory-id%2FEnglish%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2)%20For%26nbsp%3Breview%20for%20potential%20support%20escalation%20after%2024%20hours%3A%3C%2FP%3E%3CPRE%3Ehttps%3A%2F%2FOUR.COMMUNITY.DOMAIN%2Ft5%2Fbizapps%2F%3CSPAN%3Ebizappspage%3C%2FSPAN%3E%2Ftab%2Fcommunity%253Amoderation%3Ffilter%3DadminTags%26amp%3Badmin_tags%3Dmodbar.mod_review%253Areview_in_twenty_four_hrs%26amp%3Bsort_by%3D-date%26amp%3Bsearch_type%3Dmessage%26amp%3Bsearch_page_size%3D20%26amp%3Bpage%3D1%3C%2FPRE%3E%3CP%3EOur%20moderation%20team%20applies%20the%26nbsp%3Btag%20%22review_in_twenty_four_hrs%22%20to%20the%20message%20as%20they%20read%20new%20posts%20over%20the%20course%20of%20the%20day%20(1)%2C%20then%20reviews%20the%20above%20URL%20afterwards%20to%20determine%20which%20posts%20have%20exceeded%20the%20time%20threshold%20and%20need%20escalation.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20also%20use%20the%20following%20parameters%3A%3C%2FP%3E%3CUL%3E%3CLI%3E%22%26amp%3Bsearch_type%3Dmessage%22%20to%20see%20both%20topics%20and%20replies%2C%20since%20replies%20may%20also%20require%20escalation%2Fre-escalation.%20Note%20that%20as%20a%20result%2C%20we've%20effectively%20dropped%20the%20%22openresponse%3Dtrue%22%20parameter%26nbsp%3Bfrom%20our%20process.%3C%2FLI%3E%3CLI%3E%22%26amp%3Bsearch_page_size%3D20%22%20to%20control%20the%20number%20of%20messages%20on%20each%20page%20(under%2050).%3C%2FLI%3E%3CLI%3E%22%26amp%3Bpage%3D1%22%20to%20manually%20navigate%20to%20the%20right%20date%20range%20by%20page.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E3)%20For%20collection%20of%20weekly%2Fmonthly%20product%20feedback%20posts%20on%20the%20community%3A%3C%2FP%3E%3CPRE%3Ehttps%3A%2F%2FOUR.COMMUNITY.DOMAIN%2Ft5%2Fbizapps%2F%3CSPAN%3Ebizappspage%3C%2FSPAN%3E%2Ftab%2Fcommunity%253Amoderation%3Ffilter%3DadminTags%26amp%3Badmin_tags%3Dmodbar.mod_feedback%253Aproduct_feedback%26amp%3Bsort_by%3D-date%26amp%3Bsearch_type%3Dmessage%26amp%3Bsearch_page_size%3D10%26amp%3Bpage%3D1%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20moderation%20team%20applies%20the%26nbsp%3Btag%20%22product_feedback%22%20to%20the%20message%20as%20they%20read%20new%20posts%20over%20the%20course%20of%20the%20day%2C%20then%20reviews%20the%20above%20URL%20afterwards%20to%20determine%20which%20posts%20to%26nbsp%3Binclude%20in%20our%20weekly%2Fmonthly%20reports.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20also%20use%20the%20following%20parameters%3A%3C%2FP%3E%3CUL%3E%3CLI%3E%22%26amp%3Bsearch_type%3Dmessage%22%20to%20see%20both%20topics%20and%20replies%2C%20since%20feedback%20happens%20in%20both.%20As%20above%2C%20we've%20effectively%20dropped%20the%20%22openresponse%3Dtrue%22%20parameter%26nbsp%3Bfrom%20our%20process%20here%20as%20well.%3C%2FLI%3E%3CLI%3E%22%26amp%3Bsearch_page_size%3D10%22%20to%20control%20the%20number%20of%20messages%20on%20each%20page%20(under%2050)%20-%20%2210%22%20works%20best%20for%20us%20to%20allow%20for%20quick%20counts%20of%20feedback%20posts%20in%20our%20reports.%3C%2FLI%3E%3CLI%3E%22%26amp%3Bpage%3D1%22%20to%20increment%2Fmanually%20navigate%20to%20the%20right%20date%20range%20by%20page.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20that%20helps!%20Would%20love%20to%20hear%20how%20others%20are%20handling%20these%20processes%20with%20their%20teams%2C%20or%20any%20URLs%2Fparameters%20they've%20found%20or%20discovered!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-284016%22%20slang%3D%22en-US%22%3ERe%3A%20find%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-284016%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.lithium.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F51870%22%20target%3D%22_blank%22%3E%40edgiansante%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20try%20these%20URLs%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3Ehttps%3A%2F%2FYOUR.COMMUNITY.DOMAIN%2Ft5%2Fbizapps%2Fpage%2Ftab%2Fcommunity%253Amoderation%3Ffilter%3DadminTags%26amp%3Badmin_tags%3DYOURCUSTOMTAG%26amp%3Bsort_by%3D-topicPostDate%26amp%3Bopenresponse%3Dtrue%26amp%3Bsearch_page_size%3D100%0A%0Ahttps%3A%2F%2FYOUR.COMMUNITY.DOMAIN%2Ft5%2Fbizapps%2Fbizappspage%2Ftab%2Fcommunity%253Amoderation%3Ffilter%3DadminTags%26amp%3Badmin_tags%3DYOURCUSTOMTAG%26amp%3Bsort_by%3D-topicPostDate%26amp%3Bopenresponse%3Dtrue%26amp%3Bsearch_page_size%3D100%3C%2FPRE%3E%3CP%3EIn%20our%20community%2C%20the%20path%20name%20is%26nbsp%3B%3CSTRONG%3Ebizappspage%26nbsp%3B%3C%2FSTRONG%3E(2nd%20URL%2C%20after%20bizapps)%2C%20and%20%3CSTRONG%3Enot%20page.%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20unfortunately%20both%20links%20don't%20work%20in%20our%20Lithium%20community%26nbsp%3B%3CIMG%20class%3D%22emoticon%20emoticon-smileysad%22%20id%3D%22smileysad%22%20src%3D%22https%3A%2F%2Fcommunity.lithium.com%2Fi%2Fsmilies%2F16x16_smiley-sad.png%22%20alt%3D%22Smiley%20Sad%22%20title%3D%22Smiley%20Sad%22%20%2F%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20haven't%20figured%20out%20why%20it%20doesn't%20work.%20I%20guess%20it's%20due%20to%20the%20URL%20structure%20or%20configuration%20of%20the%20community.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMaybe%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.lithium.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F62789%22%20target%3D%22_blank%22%3E%40sdodds%3C%2FA%3E%26nbsp%3Bcould%20help%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%20Daniel%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-279776%22%20slang%3D%22en-US%22%3ERe%3A%20find%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-279776%22%20slang%3D%22en-US%22%3EThanks%20for%20that!%20unfortunately%20the%20URL%20is%20broken%20in%20your%20post%20-%20can%20you%20share%20it%20again%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-269925%22%20slang%3D%22en-US%22%3ERe%3A%20find%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-269925%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20those%20interested%2C%26nbsp%3BI've%20played%20around%20with%20some%20query%20string%20parameters%20in%20the%20Moderation%20tool%20to%20filter%20and%20sort%20views%20for%20us%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EURL%3C%2FSTRONG%3E%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fcommunity.lithium.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2FYOUR.COMMUNITY.DOMAIN%26gt%3B%2Ft5%2Fbizapps%2Fpage%2Ftab%2Fcommunity%253Amoderation%3Ffilter%3DadminTags%26amp%3Badmin_tags%3Dmodbar.mod_review%253Areview_in_twenty_four_hrs%26amp%3Bsort_by%3D-topicPostDate%26amp%3Bopenresponse%3Dtrue%26amp%3Bsearch_page_size%3D100%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EQSPs%20described%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CUL%3E%3CLI%3E%3CSPAN%3E%3CEM%3Efilter%3DadminTags%26amp%3Badmin_tags%3Dmodbar.mod_review%253Areview_in_twenty_four_hrs%3C%2FEM%3E%26nbsp%3B%3A%20this%20is%20filtering%20by%20the%20custom%20tag%20we%20are%20using.%20Your%20custom%20tags%20are%20likely%26nbsp%3Bdifferent%20of%20course%2C%20so%20best%20to%20select%20via%20the%20sidebar%20filter%20options.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3E%3CEM%3Esort_by%3D-topicPostDate%3C%2FEM%3E%26nbsp%3B%3A%20to%20reverse%20sort%20by%20post%20date%20to%20see%20the%20latest%20posts%20first.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3E%3CEM%3Eopenresponse%3Dtrue%3C%2FEM%3E%20%3A%20to%20return%20only%20topics%20without%20a%20response%2C%20if%20that%20is%20what%20you%20are%20looking%20for.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3E%3CEM%3Esearch_page_size%3D100%3C%2FEM%3E%26nbsp%3B%3A%20to%20see%20the%26nbsp%3Bresults%20you%20want%20on%20one%20page%20(because%20using%20the%20pagination%20controls%20removes%20any%26nbsp%3Badditional%20query%20string%20parameters%20you%20add).%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHappy%20hunting!%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-267125%22%20slang%3D%22en-US%22%3ERe%3A%20find%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-267125%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20all!%20So%20wonderful%20to%20hear%20how%20others%20are%20tacking%20similar%20problems%20-%20you've%26nbsp%3Bgiven%20me%20lots%20of%20ideas!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOne%20thing%20we%20are%20also%20trying%20out%2C%20is%20using%20custom%20tags%20to%20identify%20those%20posts%20that%20are%3A%3C%2FP%3E%3CUL%3E%3CLI%3Eimportant%20to%20be%20answered%2C%3C%2FLI%3E%3CLI%3Eand%20that%20we%20think%20the%20community%20could%20answer%2C%3C%2FLI%3E%3CLI%3Ebut%20we%20know%20we%20will%20escalate%20if%20they%20aren't.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThen%20we%20use%20the%20moderation%20tool%20to%20filter%20on%20these%20tags%20for%20any%20potential%20follow-ups.%20It's%20kind%20of%20similar%20to%20%3CA%20href%3D%22https%3A%2F%2Fcommunity.lithium.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F12041%22%20target%3D%22_blank%22%3E%40JasonHill%3C%2FA%3E's%20former%20spreadsheet%2C%20only%20we%20can%20stay%20within%20the%20community.%20Since%20we%20are%20reading%20all%20the%20messages%20anyway%2C%20this%20may%20be%20just%20as%20effective%20as%20a%20query.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-266389%22%20slang%3D%22en-US%22%3ERe%3A%20find%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-266389%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.lithium.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F62789%22%20target%3D%22_blank%22%3E%40sdodds%3C%2FA%3E%2C%20we%20have%20the%20same%20use%20case%20as%20you%20do%2C%20so%20on%20top%20of%20the%20great%20solutions%20already%20provided%20above%20perhaps%20this%20can%20help%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3EWe%20use%20the%20Salesforce%20Connector%20v3%20to%20automatically%20escalate%20unanswered%20posts%20into%20our%20Support%20case%20queue%20after%20x%20amount%20of%20time.%20You%20can%20find%20out%20more%20about%20that%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.lithium.com%2Ft5%2FIntegrating-with-Salesforce%2FAbout-the-Salesforce-and-Lithium-integration%2Fta-p%2F143292%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fcommunity.lithium.com%2Ft5%2FIntegrating-with-Salesforce%2FAbout-the-Salesforce-and-Lithium-integration%2Fta-p%2F143292%3C%2FA%3E%3C%2FLI%3E%3CLI%3EOur%20moderators%20also%20keep%20an%20eye%20on%20the%20out%20of%20the%20box%20Unanswered%20Posts%26nbsp%3Bcomponent%2Fpage%20and%20use%20time%20stamps%20as%20a%20reference%20to%20see%20what's%20been%20unanswered%20for%26nbsp%3B12h-23h%20(before%20it%20gets%20escalated%20to%20Support)%20in%20the%20event%20there%20are%20low%20hanging%20fruits%20that%20have%20existing%20solutions%20they%20can%20point%20to%20or%20share%20with%20SMEs%2Fsuperusers%20to%20take%20a%20stab%20at%20answering.%20Just%20replace%20the%20domain%20with%20your%20own%3A%20%3CA%20href%3D%22https%3A%2F%2Fcommunity.alteryx.com%2Ft5%2Fforums%2Funansweredtopicspage%2Fnode-id%2Fcommunity%253A1%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fcommunity.alteryx.com%2Ft5%2Fforums%2Funansweredtopicspage%2Fnode-id%2Fcommunity%253A1%3C%2FA%3E%3C%2FLI%3E%3C%2FOL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20this%20helps%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-266328%22%20slang%3D%22en-US%22%3ERe%3A%20find%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-266328%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20currently%20use%20a%20custom%20page%20that%20displays%20all%20unanswered%20topics%20and%20their%20last%20time%20since%20response.%20You%20could%20also%20use%20this%20to%20only%20list%20unanswered%20topics.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20checked%20LiQL%20and%20the%20API%20browser%2C%20but%20there%20is%20no%20way%2C%20currently%2C%20to%20use%20one%20query%20to%20find%20any%20message%20that%20has%200%20replies.%20The%20API%20currently%20only%20seems%20to%20support%20reply%20count%20for%20topics%2C%20in%20one%20query.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20want%20to%20find%20replies%20(non-topics)%20that%20have%20no%20further%20replies%2C%20you'd%20have%20to%20query%20a%20certain%20amount%20of%20messages%20and%20for%20each%20message%20found%20run%20an%20additional%20query%20to%20check%20its%20replies.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EE.g.%3C%2FP%3E%3CP%3ESELECT%20*%20FROM%20messages%20WHERE%20%26lt%3Binsert%20code%20for%20%22%20age%20%26gt%3B%20x%20and%20replies%20%3D%200%22%26gt%3B%3C%2FP%3E%3CP%3ELIST%20those%20results%20and%20then%20do%20something%20like%20SELECT%20count(*)%20FROM%20messages%20WHERE%20parent.id%20%3D%20'%26lt%3Bmessage%20id%26gt%3B'%3C%2FP%3E%3CP%3EThen%20do%20a%20simple%20%26lt%3B%23if%20replies%20%3D%3D%200%20etc..%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-265873%22%20slang%3D%22en-US%22%3ERe%3A%20find%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-265873%22%20slang%3D%22en-US%22%3E%3CP%3ESorry%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.lithium.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F62789%22%20target%3D%22_blank%22%3E%40sdodds%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20didn't%20pick%20up%20that%20you%20were%20also%20wanting%20to%20keep%20track%20of%20all%20posts%20(not%20just%20new%20threads)%20that%20hadn't%20received%20a%20reply.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20would%20certainly%20be%20investigating%20what%20Response%20can%20do%20for%20you.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAt%20my%20previous%20community%20we%20attacked%20this%20by%20adding%20all%20posts%20that%20required%20a%20response%20to%20a%20spreadsheet%2C%20along%20with%20the%20time%20that%20they%20were%20posted.%20The%20support%20team%20would%20then%20systematically%20work%20off%20this%20live%20Google%20doc%20from%20oldest%20to%20newest%20post.%20This%20was%20a%20foolproof%20way%20of%20being%20100%20per%20cent%20accurate%20that%20every%20single%20post%20on%20the%20community%20that%20required%20a%20response%20ended%20up%20getting%20one.%20However%2C%20this%20is%20obviously%20an%20extremely%20labour%20intensive%20process%20and%20is%20not%20recommended%20unless%20you%20have%20no%20other%20option%20-%20automated%20process%20are%20going%20to%20save%20you%20time%20and%20money%20in%20the%20long%20term!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EJason%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-265817%22%20slang%3D%22en-US%22%3ERe%3A%20find%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-265817%22%20slang%3D%22en-US%22%3E%3CP%3EI%20wonder%20if%20maybe%20I've%20been%20describing%20this%20incorrectly%20as%20an%20escalation%20problem%2C%20when%20I%20think%20it%20is%20really%20a%20problem%20with%20providing%20filtered%20views%20for%20the%20moderation%20team.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20describe%20this%20in%20more%20detail%2C%20we%20currently%20have%20the%20manual%20escalation%20feature%20configured%20using%20an%20email%20address%20that%20directly%20creates%20a%20case%20in%20a%20special%20queue%20for%20our%20Support%20team.%3C%2FP%3E%3CUL%3E%3CLI%3EWe've%20trained%20this%20team%20on%20how%20to%20respond%20in%20the%20community%20effectively.%3C%2FLI%3E%3CLI%3EAnd%20our%20moderation%20team%20is%20trained%20to%20evaluate%20different%20kinds%20of%20requests%20that%20can%20be%20escalated%20and%20answered%20in%20the%20community%20vs%20those%20that%20we%20should%20handle%20differently%20(e.g.%20community%20or%20product%20feedback%2C%20requests%20requiring%26nbsp%3Bsupport%20off%20the%20community%2C%20etc.).%3C%2FLI%3E%3CLI%3EIn%20then%20end%2C%20only%20maybe%2010-20%25%20of%20posts%20need%20to%20be%20escalated%20and%20handled%20in%20this%20fashion.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20challenge%20I%20have%20is%20that%20our%20policy%20has%20created%20two%20separate%20review%20flows%20for%20our%20moderation%20team%3A%3C%2FP%3E%3COL%3E%3CLI%3Ereview%20every%20post%20(to%20welcome%2C%20guide%2C%20thank%2C%20and%2For%26nbsp%3Bfor%20adherence%20to%20the%20terms).%3C%2FLI%3E%3CLI%3Ereview%20all%20threads%20that%20have%20not%20been%20answered%20in%2024%20hours%20or%20more.%3C%2FLI%3E%3C%2FOL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESadly%2C%20the%20moderation%20console%20and%20advanced%20search%20do%20not%20allow%20me%20to%20filter%20%3CSPAN%3Efor%20posts%20without%20a%20reply%20that%20are%2024%20hours%20old%20%3C%2FSPAN%3E%3CSTRONG%3Eor%20older%20%3C%2FSTRONG%3Eto%20cover%20the%20second%20review%20process.%3CSPAN%3E%26nbsp%3BOur%20moderation%20team%20must%20manually%20navigate%20a%20couple%20of%20pages%20forward%20in%20the%20moderation%20console%20to%20see%20the%20posts%20that%20are%2024%20hours%20old%20(or%2072%20hours%20on%20Mondays)%20and%20then%20review%20each%20message%20one%20at%20a%20time%20to%20see%20if%20any%20require%20escalation.%20It%20is%20this%202nd%20process%20that%20I%20am%20looking%20to%20simplify.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20could%2C%20as%20recommended%20by%20some%20on%20this%20thread%2C%20instead%26nbsp%3Bturn%20on%20auto-escalation%20and%20replace%20the%20email%20address%20to%20our%20support%20queue%20with%20an%20email%20alias%20monitored%20by%20our%20moderation%20team.%26nbsp%3BThen%20our%20moderators%20will%20get%20an%20email%20when%20threads%20without%20a%20reply%20are%2024%20hours%20old%20or%20older%2C%20which%20they%20can%20review%20and%20take%20appropriate%20action%20on.%20Here%20are%20my%20challenges%20with%20that%20approach%3A%3C%2FP%3E%3CUL%3E%3CLI%3EIt%20only%20works%20for%20threads%20without%20replies%2C%20and%20we%20also%20want%20to%20review%20replies%20with%20no%20response%20after%2024%20hours%20(especially%20if%20we%20actively%26nbsp%3Bwelcoming%20and%20thanking%20posters).%20Ideally%20we%20need%20to%20know%20which%20%3CEM%3Eposts%3C%2FEM%3E%20have%20no%20reply%20after%2024%20hours.%20My%20apologies%2C%20I%20realize%20I%20have%20been%20unclear%20about%20this%20in%20my%20prior%20posts%20on%20this%20thread.%3C%2FLI%3E%3CLI%3EThe%20auto-escalate%20mechanism%20doesn't%20handle%20weekends%20well%2C%20and%20our%20community%20and%20moderation%20team%26nbsp%3Bhas%20increased%26nbsp%3Bresponse%20times%20over%20the%20weekend%20-%20so%20there%20will%20be%20a%20number%20of%26nbsp%3Bauto-escalations%20that%20will%20fill%20up%20the%20inboxes%26nbsp%3Bon%20Mondays%20that%20will%20need%20to%20be%20sifted%20through%20and%20ignored.%3C%2FLI%3E%3CLI%3EIt%20takes%20the%20moderation%20team%20out%20of%20the%20community%20and%20into%20their%20email%20to%20manage%20this%20second%26nbsp%3Bworkflow.%20This%20not%20only%20reduces%20efficiency%2C%20it%20complicates%20our%20ability%20to%20add%20volunteer%20moderators%20to%20this%20process.%3C%2FLI%3E%3CLI%3EIt%20makes%20the%20escalation%20process%20to%20the%20Support%20queue%20much%20more%20manual%20(via%20email)%20or%20cumbersome%20(via%20separate%20web%20form).%3C%2FLI%3E%3CLI%3EIt%20makes%20it%20more%20difficult%20to%20measure%20the%20work%20performed%20on%20the%20second%20workflow.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20intrigued%20by%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.lithium.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F12041%22%20target%3D%22_blank%22%3E%40JasonHill%3C%2FA%3E's%20suggestion%20of%20creating%20a%20separate%20page%20for%20this%20purpose%2C%20but%20I'm%20again%20stuck%20on%20how%20I%20could%20generate%20the%20query%20to%20display%20all%20posts%20without%20a%20reply%20that%20are%20over%2024%20hours%20old.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20interested%20in%20seeing%20how%20Response%20could%20address%20this.%20I'm%20not%20sure%20a%20per%20board%20delay%20really%20addresses%20the%20issue%20-%20these%20posts%20could%20come%20in%20any%20board%2C%20really.%20And%20I%20wonder%20it%20the%20thread%20vs%20post%20limitation%20is%20still%20a%20part%20of%20this.%20From%20my%20perspective%2C%20this%20is%20less%20of%20a%20problem%20with%20escalation%2C%20and%20more%20of%20a%20problem%20with%20filtering%20views%20for%20moderation.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.lithium.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F60%22%20target%3D%22_blank%22%3E%40RobbL%3C%2FA%3E%26nbsp%3Bis%20this%20something%20Response%20can%20be%20configured%20for%3F%20Or%20ultimately%20is%20this%20a%20potential%20new%20Product%20Idea%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20if%20you%20think%20the%20problem%20is%20with%20our%20process%2C%20let%20me%20know.%20I'm%20happy%20to%20discuss%20alternatives.%20I%20may%20very%20well%20be%20making%20this%20more%20complicated%20than%20it%20has%20to%20be.%26nbsp%3B%3CIMG%20class%3D%22emoticon%20emoticon-smileywink%22%20id%3D%22smileywink%22%20src%3D%22https%3A%2F%2Fcommunity.lithium.com%2Fi%2Fsmilies%2F16x16_smiley-wink.png%22%20alt%3D%22Smiley%20Wink%22%20title%3D%22Smiley%20Wink%22%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-265538%22%20slang%3D%22en-US%22%3ERe%3A%20find%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-265538%22%20slang%3D%22en-US%22%3EHi%3CBR%20%2F%3E%3CBR%20%2F%3EIs%20your%20issue%20that%20everything%20is%20eventually%20%22escalated%22%3F%20You%20can%20configure%20in%20a%20manual%20escalation%20only%20model%20this%20will%20only%20escalate%20the%20manual%20stuff%20and%20then%20anything%20not%20answered%20after%20X%20or%20Y.%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20means%20you%20get%20anything%20with%20no%20reply%20after%20X%20mins%20and%20the%20stuff%20manually%20escaled%20givin%20you%20focus%20on%20what%20u%20need.%3CBR%20%2F%3E%3CBR%20%2F%3EAlso%20with%20regards%20to%20manual%20vs%20auto%2C%20I%20have%20an%20open%20idea%20for%20a%20marker%20or%20flag%20to%20be%20added%20to%20all%20escalations%20so%20you%20can%20see%20what%20is%20manual%20and%20what%20is%20auto%2C%20with%20response%20this%20would%20give%20you%20a%20load%20of%20extra%20routing%20options.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-265511%22%20slang%3D%22en-US%22%3ERe%3A%20find%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-265511%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fcommunity.lithium.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F62789%22%20target%3D%22_blank%22%3E%40sdodds%3C%2FA%3E%2C%20some%20Lithium%20customers%20make%20use%20of%20our%20Lithium%20Response%20product%20to%20achieve%20this%20goal.%20After%20a%20connection%20between%20Response%20and%20Community%20has%20been%20configured%2C%20the%20settings%20in%20Community%20Admin%20allow%20you%20to%20set%20per%20board%20delays%20at%20any%20level%20in%20the%20community%20hierarchy.%20For%20most%20boards%2C%20companies%20set%20a%2024%20hour%20delay%20to%20give%20their%20community%20members%20time%20to%20respond.%20On%20some%20boards%2C%20such%20as%20urgent%20support%20boards%2C%20you%20might%20want%20the%20content%20to%20come%20into%20Response%20immediately.%20If%20you%20don't%20set%20an%20explicit%20delay%2C%20posts%20are%20delayed%20by%2024%20hours%2C%20and%20if%20an%20%E2%80%9Cexpert%E2%80%9D%20has%20interacted%20with%20the%20thread%2C%2072%20hours.%20You%20specify%20which%20roles%20in%20your%20community%20constitute%20an%20%E2%80%9Cexpert.%E2%80%9D%20You%20can%20also%20give%20certain%20community%20members%20permission%20to%20override%20the%20delay%20and%20escalate%20a%20thread%20to%20Response.%20You%20can%20turn%20on%20Event%20Subscriptions%20so%20that%20posts%20in%20Response%20will%20be%20updated%20automatically%20when%20they%20are%20deleted%2C%20moved%20or%20marked%20as%20an%20accepted%20solution.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-265401%22%20slang%3D%22en-US%22%3ERe%3A%20find%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-265401%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20again%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.lithium.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F12041%22%20target%3D%22_blank%22%3E%40JasonHill%3C%2FA%3E%26nbsp%3B-%20unfortunately%20the%2024%20hour%20delay%20is%20important%20to%20us%20%3CEM%3Ebecause%3C%2FEM%3E%20we%20are%20trying%20to%20attract%20additional%20superusers.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe've%20had%20a%20habit%20in%20the%20past%20of%20responding%20too%20quickly%2C%20which%20has%20not%20given%20our%20community%20time%20to%20respond%20on%20its%26nbsp%3Bown.%20We%20want%20the%20delay%20to%20allow%20for%20community%20responses%2C%20but%20we%20want%20the%20escalation%20to%20ensure%20our%20community%20gets%20a%20response.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20page%20you%20showed%20is%20great%2C%20but%20I'm%20not%20sure%20I%20could%20use%20that%20to%20replicate%20the%20query%20on%20my%20end%20-%20are%20you%20able%20to%20share%20the%20freemarker%20code%2Fwidget%20you%20are%20using%3F%20Or%20is%20it%20using%20one%20of%20the%20existing%20components%20I%20could%20modify%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-265397%22%20slang%3D%22en-US%22%3ERe%3A%20find%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-265397%22%20slang%3D%22en-US%22%3E%3CP%3EHere's%20a%20simple%20unanswered%20posts%20page%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.lithium.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F62789%22%20target%3D%22_blank%22%3E%40sdodds%3C%2FA%3E%26nbsp%3B-%26nbsp%3B%3CA%20href%3D%22http%3A%2F%2Fcommunity.myob.com%2Ft5%2Fcustom%2Fpage%2Fpage-id%2FUnansweredPosts%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fcommunity.myob.com%2Ft5%2Fcustom%2Fpage%2Fpage-id%2FUnansweredPosts%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20wouldn't%20bother%20adding%20the%20extra%20layer%20of%20only%20showing%20posts%20over%2024%20hours%20as%20the%20timestamp%20will%20be%20so%20obvious%20and%20you%20would%20be%20able%20to%20use%20it%20for%20other%20purposes%20(eg%20sharing%20with%20superusers).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EJason%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-265390%22%20slang%3D%22en-US%22%3ERe%3A%20find%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-265390%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.lithium.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F12041%22%20target%3D%22_blank%22%3E%40JasonHill%3C%2FA%3E%26nbsp%3B-%20I'm%20using%20the%20escalations%20settings%20to%20generate%20the%26nbsp%3Bsupport%20case%2C%20and%20there%20is%20no%20way%20to%20send%20manual%20escalations%20and%20automatic%20escalations%20to%20two%20different%20email%20addresses.%20Besides%2C%20the%20desire%20is%20to%20allow%20the%26nbsp%3Bsupport%20folks%20to%20remain%26nbsp%3Bin%20their%20case%20management%20system%2C%20and%20the%20moderators%20on%20the%20community%20rather%20than%20switch%20over%20to%20email.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20custom%20page%20approach%20sounds%20interesting.%20I%20haven't%20played%20around%20with%20freemarker%20and%20custom%20queries%20there%20-%20do%20you%20know%20how%26nbsp%3BI%20would%20populate%20that%20page%20with%20only%20topics%20with%200%20replies%20that%20are%20at%20least%2024%20hours%20old%20(or%20better%20yet%2C%20an%20example)%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-265379%22%20slang%3D%22en-US%22%3ERe%3A%20find%20posts%20to%20escalate%20after%2024%20hours%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-265379%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fcommunity.lithium.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F62789%22%20target%3D%22_blank%22%3E%40sdodds%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20would%20have%20thought%20the%20automatic%20escalation%20functionality%20is%20exactly%20what%20you%20are%20looking%20for.%20You%20can%20set%20the%20timeframe%20to%2024%20hours%20(1440%20minutes)%20and%20to%20the%20email%20address%20of%20your%20choosing.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAlternatively%2C%20you%20could%20build%20a%20custom%20page%20that%20only%20features%20unanswered%20posts.%20Many%20communities%20do%20this%2C%20particularly%20for%20their%20super%20users%20and%20support%20teams.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EJason%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Honored Contributor Honored Contributor
Honored Contributor

Re: find posts to escalate after 24 hours

Would this do it?

 

<#assign user_id = user.id/>
<#assign tz = restadmin("/users/login/${user_id}/settings/name/config.timezone").value/>
<#assign beforelong = .now?long - (24 * 60 * 60 * 1000)/>
<#assign before = beforelong?number_to_datetime?iso("${tz}")/>
<#assign query = rest("2.0", "/search?q=" + "SELECT id,subject,post_time,view_href FROM messages WHERE depth = 0 AND replies.count(*) = 0 AND conversation.last_post_time <= ${before} ORDER BY conversation.last_post_time DESC LIMIT 5"?url("UTF-8")) />
<#list query.data.items as q>
	<a href="${q.view_href}">${q.subject}</a> - ${q.post_time?datetime}<br/>
</#list>

CM at Spotify
Community Ergo Sum
0 Kudos
Reply
Loading...